🚀 go-pugleaf

"Jeff Overcash (TeamB)" <overcash@onramp.net> wrote:


: Michael Mason wrote:
:> If we upgrade our hardware to a dual-CPU box, will it use both
:> the CPUs for compiling? 

: No and under W2K you will find problems in a multi CPU box and will have to set
: the CPU affinity to limit it to one CPU.

We're not worried about Win2K just yet (Service Pack 1 isn't out yet... ;)
Are you saying that if I have two source files in my project that don't depend
on each other, they will not be built in parallel?

If not, we might as well just get fast Athlons instead of Dual PIIIs.

: Check your header files.  Well designed header files will greatly reduce compile
: time.  You can look at www.bcbdev.com for a great article on constructing header
: files correctly.

I'd define "correct" header files to be ones that include only the other headers
that are actually needed. The main suggestion in that article is to lump all of
the headers used anywhere into one big header file, so it can be precompiled.
This might work, but surely it destroys any notion of modularity I once had?
Classes that previously couldn't access information defined in each other now can,
and I can make programming mistakes because of this.

So I guess I should use that technique for now, and bear in mind that every now
and again I should do a proper compile without any precompiled stuff, to check
things are right.

Cheers,
Mike.