Path: utzoo!censor!dybbuk!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!mcnc!ncsuvx!ncsugn!emigh
From: emigh@ncsugn.ncsu.edu (Ted H. Emigh)
Newsgroups: comp.lang.c++
Subject: Re: Turbo C++ & Zortech C++ memory problems
Message-ID: <6090@ncsugn.ncsu.edu>
Date: 8 Jan 91 16:54:41 GMT
Article-I.D.: ncsugn.6090
References: <6818@tekred.CNA.TEK.COM>
Reply-To: emigh@ncsugn.UUCP (Ted H. Emigh)
Organization: North Carolina State University, Department of Genetics
Lines: 30

In article <6818@tekred.CNA.TEK.COM> waynet@tekred.CNA.TEK.COM (Wayne Turner) writes:
>We are developing a commercial application under DOS using
>Turbo C++ Version 1.01 and are consistently running into "Out
>of memory", "Not enough memory" errors from the command-line
>versions of the compiler and linker. The application itself is
>not huge--the source consists of about 5-6K lines and the
>current .EXE takes up about 360K bytes when loaded.

....

>Other pertinent info:
>Using large memory model 
>Using debugging option for all modules (we don't know in 
>advance what modules will need debugging :-)

My comment has to do with his last statement.  I have a large project which
I maintain (sounds about the same size as his).  I turn on debugging ONLY
for the module which contains main{} and any others which I am currently
debugging.  A well-designed project should allow you to be able to turn on
debugging for a couple of modules at a time.  I have three makefiles -- one
which turns on debugging info for ONLY the main{} module; one which turns
on debugging info for ALL modules; and one which turns off debugging info
for ALL modules.  When I change the headers or want to rebuild the program,
I use the first.  When I want to turn on debugging for a module (test.c),
I delete test.obj, then use the second makefile.  When I want to turn off
debugging for a module (test.c), I delete test.obj, then use the last
makefile.

(Note: all makefiles have link set up to include debugging information.  I
also have a "production" makefile which doesn't link debugging information.)