CompuServe Messages

Andrew, "I gather that the connection between the preprocceser and the compiler in Symantec C++ is completely closed and private?" I don't know the internals of the Symantec compiler, but there is no separate pre-processor as in an AT&T style C++ pre-processor which spits out C code. Obviously, there's some internal magic happening to deal with classes & defines, but yes, it is seen by the user as a completely enclosed unit. Do other native C++ compilers (as opposed to CFront-style pre-processors) work differently than this? "Making real changes in source files in not going to work. Too delicate." I'm a bit befuddled by why you think massaging paths in a source file is more delicate than patching file traps or massaging paths at compile time, but that's your call. Good luck! It's good to hear that you had some support for the macro idea. Reede