Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!usc!bloom-beacon!bu-cs!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: effect of free()
Message-ID: <10732@smoke.BRL.MIL>
Date: 14 Aug 89 19:44:09 GMT
References: <319@cubmol.BIO.COLUMBIA.EDU> <3756@buengc.BU.EDU>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 5

In article <3756@buengc.BU.EDU> bph@buengc.bu.edu (Blair P. Houghton) writes:
>Yes.  It can now be allocated to something else.  It is _not_,
>however, cleared or otherwise overwritten by free(), ...

It can be; that's implementation dependent.