From: stockton AT bcm DOT tmc DOT edu (David Stockton)
Message-Id: <199701101926.NAA21023@ginger.imgen.bcm.tmc.edu>
Subject: Re: Malloc & Co.
To: djgpp AT delorie DOT com (DJGPP Mail List)
Date: Fri, 10 Jan 1997 19:26:23 +0000 (GMT)
Cc: fighteer AT cs DOT com
In-Reply-To: <32D20E0F.5AB0@cs.com> from "John M. Aldrich" at Jan 7, 97 00:49:19 am
Reply-to: stockton AT bcm DOT tmc DOT edu
Organization: Molecular and Human Genetics, Baylor College of Medicine
Phone: (713)798-4795
x-fax-number: (713)798-5073
x-phone: (713)798-4795
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> John M. Aldrich wrote:
> All memory that is allocated using sbrk(), malloc(), and its family, is
> automatically freed by the DJGPP exit code.  It is, however, generally
> good programming to clean things up yourself (although very few

I am not sure I agree with this statement.  Why should the user have to
sit around and wait while some programs traverses all its arrays and
linked lists freeing memory when it will make no difference at all?  I
agree that keeping track of allocations and being able to free them during
execution to prevent "core leaks" is imperitive, but before termination -
why bother!
					- David