Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!gatech!uflorida!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: Re: Malloc problems
Message-ID: <7897@brl-smoke.ARPA>
Date: 15 May 88 19:32:46 GMT
References: <272@marob.MASA.COM> <690008@hpfelg.HP.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <690008@hpfelg.HP.COM> jk@hpfelg.HP.COM (John Kessenich) writes:
>        2.  Free does not necessarily return memory for malloc's
>		immediate re-use.

In any reasonable implementation, it does.

The only wrinkle is that some implementations promise that an
immediately-following realloc() on the freed block will work, but
the freed block IS available immediately for re-use; this is just
a special weird case of re-use.  A malloc() after a free() is
expected to be able to return a pointer to a block containing
some or all of the freed block.