X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Fri, 17 May 2002 10:05:18 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <9743-Fri17May2002100518+0300-eliz@is.elta.co.il>
X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <3CE41EB8.619484D9@yahoo.com> (message from CBFalconer on Thu, 16
	May 2002 17:03:52 -0400)
Subject: Re: Malloc/free DJGPP code
References: <10205161914 DOT AA17309 AT clio DOT rice DOT edu> <3CE41EB8 DOT 619484D9 AT yahoo DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Date: Thu, 16 May 2002 17:03:52 -0400
> From: CBFalconer <cbfalconer AT yahoo DOT com>
> > 
> > It might be possible to make sbrk() return these blocks to DPMI, but
> > I have no plans to revisit that ugly assembler code unless something's
> > badly broken.
> 
> It should be totally unnecessary, because the malloc code is the
> only access to sbrk provided in the whole system (barring emacs). 

Emacs is not the only program that uses sbrk directly.

Also, don't forget that there are other programs running on the same
box, at least if you run on Windows.  So returning unused memory to
the OS would be a Good Thing.