Re: Compilation speedup trick: any side-effects?

borphi@[EMAIL PROTECTED]
 wrote:

> 
> So to summarize it:
> 
> Concatenating all cpp files to one big one possibly breaks
> compilation, but if this is fixed (no conflicts), there should be no
> unexpected conflicts during linking or execution (am I right?). The
> order of execution of static objects switches from undefined to
> defined, but as long as the official build is made traditionally, no
> one should rely on it anyway!
> 
NO! The dangerous case is where your compiler compiles the code but to
do something different from what was intended and than would have been
done with separate compilation.

The fact that that might not happen very often is a serious issue
because it means that when it does happen it is likely to go undetected
for some time and when errors show up you will have no idea where to
look for the cause.

The concatenation of anonymous namespaces is a serious issue as this is
where experienced developers place there helper tools for specific
cl*****.

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]