Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!samsung!ginosko!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.bugs.sys5
Subject: Re: closedir() bug report (SVr3.1)
Message-ID: <11418@smoke.BRL.MIL>
Date: 27 Oct 89 16:59:57 GMT
References: <89Oct23.223414edt.2151@neat.cs.toronto.edu> <5890003@hpcupt1.HP.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <5890003@hpcupt1.HP.COM> vandys@hpcupt1.HP.COM (Andrew Valencia(Seattle)) writes:
-	... 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.

On the other hand, no code should be written to depend on this "guarantee".
Thus closedir() really did have a bug (I should know; I wrote it).