From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,13d6cd0af0d0d769
X-Google-Attributes: gid103376,public
From: Theodore Dennison <dennison@escmail.orl.mmc.com>
Subject: Re: Does memory leak?
Date: 1995/03/28
Message-ID: <3l93dg$o8v@theopolis.orl.mmc.com>#1/1
X-Deja-AN: 100540710
references: <3kopao$ekg@nef.ens.fr> <EACHUS.95Mar22193719@spectre.mitre.org>
 <3kvccb$18ru@watnews1.watson.ibm.com>
to: ncohen@watson.ibm.com
content-type: text/plain; charset=iso-8859-1
organization: IPL InterNetNews site
x-url: news:3kvccb$18ru@watnews1.watson.ibm.com
mime-version: 1.0
newsgroups: comp.lang.ada
Date: 1995-03-28T00:00:00+00:00
List-Id: <comp.lang.ada>

Robert I. Eachus <EACHUS.95Mar22193719@spectre.mitre.org> writes:
> In article <EACHUS.95Mar22193719@spectre.mitre.org>,
> eachus@spectre.mitre.org (Robert I. Eachus) writes:
> 
> It sounds as if the case you are talking about involves a bounded amount
> of storage allocated ONCE at the beginning of the program.  As long as it
> does not cause memory to gradually become exhausted as execution
> continues, I don't call that a leak either.
> 

.unless your package ends up running on a platform without virtual memory.
Many of the smaller O.S.'s don't have the ability to recover this memory when
a program terminates. If there is any chance your code might be re-used on
such a platform, please do not code this way! At least deallocate this memory
upon program termination (and don't forget those exception handlers).

T.E.D. (structured programming bigot)