From:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Large arrays eating disk space
Date:	13 Oct 1997 06:38:51 GMT
Organization:	The National Capital FreeNet
Lines:	22
Message-ID:	<61sflr$fq8@freenet-news.carleton.ca>
References:	<Pine DOT GSO DOT 3 DOT 94 DOT 971012124635 DOT 6579A-100000 AT minerva DOT cis DOT yale DOT edu> <61r459$dkh AT sjx-ixn4 DOT ix DOT netcom DOT com>
Reply-To:	ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire)
NNTP-Posting-Host:	freenet3.carleton.ca
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

firewind (firewind AT metroid DOT dyn DOT ml DOT org) writes:
> J. Hormuzdiar <jimh AT pantheon DOT yale DOT edu> wrote:
> 
>> Hello-
>> 	Perhaps this question is better intended for comp.lang.c, but I am
>> not sure yet.
> 
> It is not on-topic for comp.lang.c; how a compiler stores fixed-length
> arrays has nothing to do with the C language.

So? This is comp.os.msdos.djgpp, a specific compiler with a specific
implementation of statically allocated arrays. (IMHO, if the array isn't
initialized where declared, or is huge, the compiler should translate it
silently into a runtime allocation and at exit deallocation, with some
initializing code...but I digress...)

--
    .*.  Where feelings are concerned, answers are rarely simple [GeneDeWeese]
 -()  <  When I go to the theater, I always go straight to the "bag and mix"
    `*'  bulk candy section...because variety is the spice of life... [me]
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca, http://chat.carleton.ca/~pderbysh

- Raw text -