Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hplabs!hpl-opus!hpnmdla!john
From: john@hpnmdla.hp.com (John McLaughlin)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Using Borland C++
Message-ID: <13750001@hpnmdla.hp.com>
Date: 12 Apr 91 17:51:36 GMT
References: <1991Apr5.171426.28904@SanDiego.NCR.COM>
Organization: HP Network Measurements Div, Santa Rosa, CA
Lines: 20

In comp.windows.ms.programmer, jerry@polygen.uucp (Jerry Shekhel) writes:


>    I have a question about pre-compiled headers.  This feature is a miracle,
>    but it seems like a new header image (.SYM) needs to be created during the MAKE
>    process whenever a file is compiled which includes a set of headers which is
>    different from the current .SYM image.  In other words, the project maintains
>    only one .SYM image.  So if your project contains two files, each including
>    a different set of headers, turning on the pre-compiled header option doesn't
>    save you any time.  Is there a way around this, so that the project can
>    handle multiple .SYM files (disk space is not a problem)?


Yes, I am glad someone else was seeing this problem.  I have been trying
(unsuccesfully) to let every 'module' in a project file have
it's own pre-compiled header (using #prama hdrfile "myfile.sym" and
#pragma hdrstop) I have had zero luck however.  Although pre-compiled
headers are great! they become much less usefull when used as part of a 
large multi file project.  Does anyone know a workaround?
-John