Date: Tue, 18 Mar 2003 08:29:22 +0200
From: "Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <1190-Tue18Mar2003082921+0200-eliz@elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <3E74E454.BC734243@yahoo.com> (message from CBFalconer on Sun, 16
	Mar 2003 15:53:40 -0500)
Subject: Re: nmalloc revisited
References: <200303141601 DOT RAA26911 AT lws256 DOT lu DOT erisoft DOT se> <3E721051 DOT 645AA67D AT yahoo DOT com> <3E74B558 DOT 3629CBA9 AT yahoo DOT com> <1438-Sun16Mar2003203300+0200-eliz AT elta DOT co DOT il> <3E74E454 DOT BC734243 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: Sun, 16 Mar 2003 15:53:40 -0500
> From: CBFalconer <cbfalconer AT yahoo DOT com>
> > 
> > libc/malloc.h is new with the development version of the library, so
> > you can only find it in the DJGPP CVS.
> 
> Then why is anyone worrying about compatibility with it?

Because those functions weren't coded to some arbitrary specification,
they follow the external API of their namesakes that are available on
many Unix systems.  I believe the docs says so.