Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Memory Allocation (was Re: binary data files)
Message-ID: <10202@smoke.BRL.MIL>
Date: 4 May 89 04:12:58 GMT
References: <10946@bloom-beacon.MIT.EDU> <12546@ut-emx.UUCP> <29978@apple.Apple.COM> <17252@mimsy.UUCP> <1989May3.201118.10221@utzoo.uucp>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <1989May3.201118.10221@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>In article <17252@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>>I get the feeling that some future BSD will have six different malloc
>>library routines. . . .
>It would be too much to ask for one *good* one!  :-) :-(

Most applications that really care about malloc() efficiency have already
given up and implemented their own technique, using malloc() simply as an
sbrk() surrogate.