Originally Posted by
matsp
Because of the way that the compiler handles precompiled headers is that way - I presume what it actually does is load the precompiled header(s) into the internal tables first, then start parsing the rest of the code.
It is an error to attempt to compile one module with precompiled headers and another module without. So don't do that.
Edit: Note Elysia expands on this - it is possible, as long as you use the correct settings for each file, to have some files include the precompiled headers, and other files to NOT do that. However, we now come to a contentious issue of "what use is precompiled headers if they are not used in all [or at least most] source files?
--
Mats