Xref: news2.mv.net comp.os.msdos.djgpp:6582
Newsgroups: comp.os.msdos.djgpp
From: Peter Berdeklis <peter AT atmosp DOT physics DOT utoronto DOT ca>
Subject: Re: Flat Memory Questions 
Message-ID: <Pine.SGI.3.91.960730103019.8069A-100000@chinook.physics.utoronto.ca>
Nntp-Posting-Host: chinook.physics.utoronto.ca
Sender: news AT info DOT physics DOT utoronto DOT ca (System Administrator)
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Organization: University of Toronto - Dept. of Physics
In-Reply-To: <31fd8516.sandmann@clio.rice.edu> 
Date: Tue, 30 Jul 1996 14:33:46 GMT
References: <720 DOT 9607281807 AT ws-ai5 DOT dur DOT ac DOT uk> <31fd8516 DOT sandmann AT clio DOT rice DOT edu> 
Lines: 19
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On Mon, 29 Jul 1996, Charles Sandmann wrote:

> > Array is now static: ie a 1Mb array is made inside your executable, working but
> > leading to a bloated >1Mb executable!
> 
> The bloat should only happen with C++, and can be avoided with a command line
> switch.

What does the array being static have to do with using C++?  Any static 
variable must have memory space preallocated, either in the initialized 
data segment (=1 Mb bloat) or in the uninitialized segment (no bloat).  
What am I missing Charles?

Pete

---------------
Peter Berdeklis
Dept. of Physics, Univ. of Toronto