Path: utzoo!attcan!uunet!crdgw1!antarctica!davidsen
From: davidsen@antarctica.crd.GE.COM (william E Davidsen)
Newsgroups: comp.lang.c
Subject: Re: validity of free() on later pointer operations
Message-ID: <9633@crdgw1.crd.ge.com>
Date: 11 Jul 90 19:01:54 GMT
References: <1990Jul3.185032.8434@indetech.com> <1990Jul03.233255.2616@virtech.uucp> <1956@runxtsa.runx.oz.au>
Sender: news@crdgw1.crd.ge.com
Reply-To: davidsen@crdos1.crd.ge.com
Organization: GE Corporate R&D Center, Schenectady NY
Lines: 13


In article <1956@runxtsa.runx.oz.au>, edward@runxtsa.runx.oz.au (Edward
Birch) writes:

|> I quote the manual here:
|> 	The argument to "free" is a pointer to a block previosly allocated
|> 	by "malloc"; after "free" is performed this space is made available
|> 	for further allocation, but its contents are left undisturbed.

  I'm not sure what manual you think is "the" manual, K&R 2nd ed.
doesn't say that (pg 252), nor does my copy (admiditedly a draft copy)
of the ANSI standard. What athority are you quoting? This sounds like
some vendor nonportability from an early UNIX version.