CompuServe Messages

Dave, You're not being stubborn, just confusing issues of portability with issues of architectural design. Portability issues generally (but not always) involve trade-offs. As an example, when I'm writing a program for which I don't give a hoot about portability, I'll generally use the Amiga-specific DOS file calls Open(), Read(), Write(), etc. rather than using the (almost) equivalent open(), read, write() functions of the "standard" library. It's more efficient. Of course, when I'm writing with portability in mind, I'll accept the extra overhead and use the standard library functions 'cause it's more portable. I agree that the differences between Manx and Lattice regarding the manner in which Graphics-memory-specific data is handled leads to having to redesign (to make optimal use of the architectural implementations). I bit that bullet when I converted my 1+ meg source code. It wasn't a matter of portability, however. In fact, I did the conversion to Manx first and got it working (albeit less efficiently), and _then_ addressed the design issues. …BobR P.S. – Sorry about the time-lag in reply. I was out-of-town for the weekend and have a bit of catching-up to do with the message base! <argh>