Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: A tale of two C's.
Message-ID: <7820@brl-smoke.ARPA>
Date: 3 May 88 13:56:07 GMT
References: <152@ghostwheel.UUCP> <7691@brl-smoke.ARPA> <154@ghostwheel.UUCP> <7750@brl-smoke.ARPA> <474@bnlux0.bnl.gov> <488@sas.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 5

In article <488@sas.UUCP> bts@sas.UUCP (Brian T. Schellenberger) writes:
>Second of all, if you don't like the normal memory allocation routines, you
>can write and use your own quite portably.

The only safe way to do this is to make your private memory allocator
obtain heap space from the standard C library allocator (malloc).