Xref: utzoo comp.std.c:963 comp.lang.c:17297
Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!rochester!pt.cs.cmu.edu!andrew.cmu.edu!bader+
From: bader+@andrew.cmu.edu (Miles Bader)
Newsgroups: comp.std.c,comp.lang.c
Subject: Re: realloc
Message-ID: <cYAd3My00UkaI1vvZr@andrew.cmu.edu>
Date: 30 Mar 89 20:40:56 GMT
References: <10170@bloom-beacon.MIT.EDU>,
	<681@sdrc.UUCP>
Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA
Lines: 8
In-Reply-To: <681@sdrc.UUCP>

scjones@sdrc.UUCP (Larry Jones) writes:
> And when handed a non-NULL pointer and a zero size, it acts like
> free.  This behavior is required by the draft ANSI Standard.

Does it return NULL in this case (when it acts like free)?  If so, how
extra-ordinarily convenient...

-Miles