Re: Semantic difference of source files

On 2008-08-23, Hans-Peter Diettrich <DrDiettrich1@aol.com> wrote:
> A project-wide compilation has another benefit, with regards to global
> compiler or project settings. Once the public part of a module has
> been parsed, with the current settings applied, it doesn't deserve
> another parse throughout the remaining compilation. The weak
> relationship between C header files and source modules, and IMO in
> detail the introduction of namespaces in C++, prevents the
> determination of common public information, that *should* be kept in
> memory.


It's alos the fact that the preprocessor is used less heavily, and doesn't
flow over module borders.


IOW if module A uses module B and module C uses B, the compilation is
generally independant of the preprocessor state (or any state state
actually) of A and C at the moment of including/using.


Most Pascal compilers of course implement some checks to emit warnings if
preprocessor state deviates (to detect incomplete builds, and hint to the
programmer that a full build is in order), but this is magnitudes less
complicated.

Return to the comp.compilers page.
Search the comp.compilers archives again.