Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.lang.c Subject: Re: Life after free? Message-ID: Date: 7 Oct 90 20:55:32 GMT References: <6573.tnews@templar.actrix.co.nz> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 11 In article <6573.tnews@templar.actrix.co.nz> jbickers@templar.actrix.co.nz (John Bickers) writes: > Quoted from - kaleb@thyme.jpl.nasa.gov (Kaleb Keithley ): > > Which OS is that on? At the risk of exhibiting "small world" syndrome, > > in UNIX, malloc and free work within the confines of the heap, which > The Amiga's Exec, for example. In every implementation of malloc and free I know of on the Amiga, a free does not return the pointer to the O/S. A FreeMem does, but that's not a standard C routine. And I'm pretty sure a FreeMem doesn't scribble on the data freed, nor does AllocMem guarantee an empty block. -- Peter da Silva. `-_-' +1 713 274 5180. 'U` peter@ferranti.com