effect of free()

[Chris Torek]

In article <10817 at riks.csl.sony.co.jp> diamond at csl.sony.co.jp (Norman Diamond)
writes:
>... a freed pointer is still valid in a call to realloc
>(as long as there are no intervening *alloc calls), and the data still
>have to be sitting in limbo, not really quite freed yet.

This is a feature of certain Unix implementations, and is not true in
general.  (It is even false in some Unix implementations.  It was, more
or less, a bit of sloppiness that got documented and hence labelled
Official, and then it was too late to fix it painlessly.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris at mimsy.umd.edu	Path:	uunet!mimsy!chris