Re: Compilation speedup trick: any side-effects?

On 25 Kwi, 19:13, bor...@[EMAIL PROTECTED]
 wrote:

> The question is: once it compiled successfully (no duplicate
> definitions etc)

The problem is that it does not have to compile successfully in this
context - the unnamed namespaces will effectively get merged and the
objects with internal linkage will see each other as well. This can
lead to conflicts that might not have existed with separate
translation units.

> There is one issue I already can think of: the order of the execution
> of constructors of static objects (like global variables).

This is not an issue - on the contrary, the order will get fixed by
the algorithm that you use in your script to order C++ files for
concatenation. This is better (more control) than what the standard
guarantees for separate translation units.

In any case, your trick has natural limitation in terms of scalability
- the compiler has to crunch N times more source text at a time than
normally. Look around for bigger hardware.

--
Maciej Sobczak * www.msobczak.com * www.inspirel.com

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