🚀 go-pugleaf

Fernando  <frr@easyjob.net> wrote:

>On Wed, 7 Jan 2004 10:54:08 -0800, "Remy Lebeau \(TeamB\)"
><gambit47.no.spam@no.spam.yahoo.com> wrote:
>
>>You should not include the Windows headers before the #pragma hdrstop
>>statement.  That prevents the project from being able to use the VCL's
>>default precompiled headers correctly (if you have PCH enabled, that is).
>>Include them after the statement instead:
>>
>>    #include <vcl.h>
>>    #pragma hdrstop
>>    #include <windows.h>
>>    #include <shlobj.h>
>
>I though I was suposed to put header files that don't change very often before
>the pagma. Is this incorrect?

Well, this is one place where I'll disagree with Gambit.

What _I_ do looks like this:

  #include "PrecompiledHeaders.h"
  #pragma hdrstop

and then I set the IDE compiler options to cache the pre-compiled
headers in the same directory as the object files. The first file takes
a little longer to compile, but with a few dozen files compiling at less
than a second apiece, it's probably works out quicker than just
precompiling vcl.h.

I tend to #include any standard headers used by any sources in the
project into that header file, so it currently includes 34 headers,
including one that's 7 MB in its own right. (But not vcl.h, since it's a
pure Windows project.)

Some figures:

  Contents commented out - 60 files in 120 seconds
  Contents left in       - 80 files in 55 seconds (inc precompilation) 

What you _don't_ want to do, though, is to have different file sets
before the #pragma hdrstop. That will produce slowdowns, as the system
realises that the last file set was inconsistent with what's wanted this
time.

Alan Bellingham
-- 
Team Mongolian Wok
<url:http://www.borland.com/newsgroups/> Borland newsgroup descriptions
<url:http://www.borland.com/newsgroups/netiquette.html>      netiquette