CompuServe Thread

Andrew, "Specificly what I want to do is to add a pre-pre-proccesser step. I want to massage the source, then let Symantec C++ take over." This is still your path problem, right? There are a couple of scripting-type things you might try. I'm going to talk about Frontier since that's what I know and like the best. I'll leave AppleScript comments to someone else. With Frontier menu-sharing you can specify command-keys. What that would essentially allow you to do is invoke any script as an override to cmd-U or cmd-K. Then you could invoke the compile or bring-up-to-date from the script. You could write either a UCMD or a simple AppleEvent-driven program to parse your files making the necessary changes. One gotcha with this is that I do not believe TPM can be queried about header files (makes sense — they're not in the project and are only visible when parsed), so you would have to find them yourself. This strategy obviously has the drawback you were hoping to avoid — modification (at least temporarily) of source files. If I were going to try to solve this problem, I think I would adopt a slightly different strategy. Essentially, I would try to drive or hook into the process of moving your files to and from their unix homes. A Frontier agent can monitor the contents of a folder searching for new files. What I might try is to set up such an agent to convert the paths when files are moved in. Then re-convert the paths when they are moved out. Frontier has file read and write routines, but they're really not meant for high volume stuff, so you'd probably want to write your own parser which can be invoked by the script. If you handle it this way, you don't have to intervene in the build/link process at all. Once again, though, you'd obviously be modifying source code. Reede