CompuServe Messages

<< With the compilers you encountered, what were the conflicts with quotes versus <>? I "solved" this in Think C by placing my root directory within the Think folder. On the Amiga, the compiler is much more Unix-like, and I placed the directory name in an enviroment search path variable. >> Some files we use have want the system path, others expect to find files locally. Just trying to adapt to standard conventions. The less I have to change the better. I've got about 20 programmers to keep happy with these 'rules' on about 4 type computers. << Can you tell me about other portability issues you addressed? >> We are trying hard to stay within POSIX rules. I wrote an almost complete POSIX library for the Macintosh which provides most POSIX file handling calls. It supports all directory handling, path names with slashes in 'fopen' etc. It supports directory creation and deletion (Creates _FULL_ path name provided!). I have also written a simple graphics API which supports X and Mac calls. It is enough for my geography ploting software to plot detailed world maps. It does _NOT_ support windowing calls, only grahpics. There is _NO_ offical support for the Macintosh where I work. Our current release only runs on the Macintosh, but our new version is UNIX only (SUN mostly, eeechhh!). It will work under AUX, but that is not a requirement. The Airforce thinks the Macintosh is that evil 'M' machine. I want as much to run on the Mac as possible to make my development easy. If it will run on the Mac _AND_ Unix, then it is truely portable! If you have any specific questions about how we work, I'd be glad to talk with you. Cheers! ——- Andrew