🚀 go-pugleaf

In article <1991Apr11.162855.10164@SanDiego.NCR.COM> davel@booboo.SanDiego.NCR.COM (David Lord) writes:
>davel@booboo.SanDiego.NCR.COM (David Lord) (that's me!) writes:
>
>>1) Linking even a minimal Windows program on my 386SX takes twenty minutes.
>>   Using Hyperdisk in Staged Write mode will cut the time down to about five.

Solution:
>3) Run BCX (protected mode compiler).
>
>	This means running Windows in REAL mode. Sounds awful, but I'll...

BZZT!  Wrong, but thanks for playing. (Oh, sorry, I thought this was
comp.lang.c)

To run BCX (the _protected_ mode compiler), you must run windows in
_protected_ mode (win /s).  I wouldn't use Windows in real mode.
RTM (_User's Guide_, p.4) about running BC++ in protected mode.

>In article <1038@stewart.UUCP> jerry@stewart.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.  ...(stuff deleted)...
>
>Use the same headers in each module :-). Actually I think only the first few
>have to be the same.

The one .SYM file keeps the data for _all_ previously compiled
modules.  You know when BC++ uses a pre-compiled header because
the compiler spits out a message.  See Appendix A in the _User's
Guide_ for more info. about Precompiled Headers.

I would say RTFM, but I understand how difficult it is to figure out
which Borland manual has the information you want (am I a User or a
Programmer?).

Jamshid Afshar
jamshid@emx.utexas.edu

PS: Precompiled headers are really great, but their usefulness in
large projects is kinda limited because, for example, almost none of
my modules include the same headers or include them in the same order.
This means the SYM file has to have a separate entry for each module
(over 100) with each entry containing alot of duplicate information.
I wish Borland would find a way to just precompile a .h file instead
of a set of includes statements.  I don't do anything fancy in header
files, so I don't mind restrictions.  Know what I mean?