Newsgroups: comp.std.c
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: free behavior (was: Re: Out-of-bounds pointers)
Message-ID: <1989Oct10.170456.6312@utzoo.uucp>
Organization: U of Toronto Zoology
References: <1009@mtxinu.UUCP> <12570028@hpclwjm.HP.COM> <868@crdos1.crd.ge.COM> <217@bbxsda.UUCP> <11234@smoke.BRL.MIL> <17119@rpp386.cactus.org>
Date: Tue, 10 Oct 89 17:04:56 GMT

In article <17119@rpp386.cactus.org> jfh@rpp386.cactus.org (John F. Haugh II) writes:
>Doesn't free() insure the pointer remains valid until the next
>call to malloc()...

No.  Some Unix implementations guaranteed this; ANSI C does not.
-- 
A bit of tolerance is worth a  |     Henry Spencer at U of Toronto Zoology
megabyte of flaming.           | uunet!attcan!utzoo!henry henry@zoo.toronto.edu