From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10211302010.AA15154@clio.rice.edu>
Subject: Re: malloc()s
To: djgpp-workers AT delorie DOT com
Date: Sat, 30 Nov 2002 14:10:44 -0600 (CST)
In-Reply-To: <200211300929.gAU9Tu114794@speedy.ludd.luth.se> from "ams@ludd.luth.se" at Nov 30, 2002 10:29:56 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> In src/libc/ansi/stdlib/ there is bsdmallo.c which looks like some old
> malloc implementation which isn't used.
> 
> Should it be removed? 

No.  Different mallocs have different strengths and weaknesses.  

> Or should we add CBFalconer's malloc as cbfmallo.c.

This might be a way to store the code until we get it upgraded ...

Eventually it should be malloc.c with the current one being
djmalloc.c, but we're not ready yet

> If we just add them with new names we have the nice ability to switch
> which one we want by changing one line in the makefile.

Or someday allow multiple mallocs just by a different -lbsdmalloc,
or -ldjmalloc