Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!mit-eddie!husc6!mailrus!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.UUCP Newsgroups: comp.unix.wizards Subject: Re: Speaking of ksh Message-ID: <8014@brl-smoke.ARPA> Date: 4 Jun 88 21:54:06 GMT References: <300@hi3.aca.mcc.com.UUCP> <894@xyzzy.UUCP> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 13 In article <894@xyzzy.UUCP> meissner@xyzzy.UUCP (Michael Meissner) writes: >In a similar note, I wish that programs would stop replacing >internals of the library, or at least make it an option to >use the default routines. Hear, hear! At the very least, they should let the C library operate the way it was designed, and use different names for the application's special versions of things like malloc(). UNIX C library malloc() implementations that I have seen are careful to allow other uses of the heap space, so a separate allocator can do its thing without interfering with malloc() (and vice-versa).