Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!purdue!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!apple!motcsd!hpda!hpcupt1!vandys
From: vandys@hpcupt1.HP.COM (Andrew Valencia(Seattle))
Newsgroups: comp.bugs.sys5
Subject: Re: closedir() bug report (SVr3.1)
Message-ID: <5890003@hpcupt1.HP.COM>
Date: 24 Oct 89 16:29:11 GMT
References: <89Oct23.223414edt.2151@neat.cs.toronto.edu>
Organization: Hewlett Packard, Cupertino
Lines: 15

/ hpcupt1:comp.bugs.sys5 / rayan@cs.toronto.edu (Rayan Zachariassen) /  7:34 pm  Oct 23, 1989 /
>stored within it.  The semantics of free doesn't guarantee data
>integrity of freed memory.

From some fairly System-Vish man pages for malloc/free:

	The argument to free is a pointer to a block previously allocated
	by malloc; after free is performed this space is made available
	for further allocation, but its contents are left undisturbed.
				=====================================

You can claim that this is WRONG, but for compatibility I'd recommend not
going against the grain with alternative malloc/free implementations.

					Andy