🚀 go-pugleaf

In article <1991May2.192124.26449@unlv.edu>, whitney@sunnyland.cs.unlv.edu (Lee Whitney) writes:
|> In article <1991Apr12.154854.29070@SanDiego.NCR.COM>, davel@booboo.SanDiego.NCR.COM (David Lord) writes:
|> ) From: davel@booboo.SanDiego.NCR.COM (David Lord)
|> ) Subject: Re: Using Borland C++
|> ) Date: 12 Apr 91 15:48:54 GMT
|> ) Organization: NCR Corporation, Rancho Bernardo
|> ) 
|> ) 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.
|> ) 
|> )  To all those people who kept telling me to run the compiler in protected
|> )  mode: you were right.
|> ) 
|> )  The program I'm working on took 8 minutes to link in normal mode,
|> )  4 minutes with Hyperdisk in staged write mode, and 6 SECONDS when
|> )  I run the compiler in protected mode, and that's running under Windows.
|> ) 
|> )  Color me astounded. I would kind of like to know where all that extra
|> )  time is going in normal mode.
|> ) 
|>     Really!
|> 
|> 	Why is protected mode an excuse?  The Turbo C 2.0 linker was lightning fast in real mode, so obviously it's possible to avoid at least an unreasonable delay.  That kind of link speed is not even livable let alone likable.




Also, you will notice a very large speed difference when you turn debugging
information off.  I'm talking VERY LARGE!  Unfortunately, not many people can
write large applications without needing the debugger at least once!


-- 

Jody Hagins             
hagins@gamecock.rtp.dg.com    
Data General Corp.      
62 Alexander Dr.        
RTP, N.C.  27709        
(919) 248-6035          

Nothing I ever say reflects the opinions of DGC.