CompuServe Messages

Thanks for the reply about inserting myself into the compile cycle. You were on target about doing this for the "slash in path name" issue. My hope had been to, in effect, pipe source through me to the pre-proccesser makeing changes as needed. Under UNIX this would not have been hard. Making real changes in source files in not going to work. Too delicate. I gather that the connection between the preprocceser and the compiler in Symantec C++ is completely closed and private? My three options now: 1) Try some compile time trick to massage the path names. 2) Patch the File Traps to accept path names with slashes. 3) Use some kind of portable macro to build include paths. 4) Pray Bedrock will actually allow me to use the tools that even the DOS world takes for granted. 5) Ignore the problem. There has actually been a tiny little bit of support for option 3 at work, (Suprise!). I would prefer option 1, as it is the most elagant. Option 2 is probably the path of destruction. Oh well, thanks anyway! Cheers! 🙂 —— Andrew