Xref: utzoo comp.std.c:981 comp.lang.c:17343 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!sdrc!scjones From: scjones@sdrc.UUCP (Larry Jones) Newsgroups: comp.std.c,comp.lang.c Subject: Re: realloc Message-ID: <686@sdrc.UUCP> Date: 31 Mar 89 23:12:32 GMT References: <10170@bloom-beacon.MIT.EDU>, Organization: Structural Dynamics Research Corp., Cincinnati Lines: 19 In article , bader+@andrew.cmu.edu (Miles Bader) writes: > 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... It's implementation defined -- the implementation is allowed to return either a NULL pointer or a pointer to a zero-sized object (although many people find that concept quite repugnant, that's the way many existing implementations behave). ---- Larry Jones UUCP: uunet!sdrc!scjones SDRC scjones@sdrc.UU.NET 2000 Eastman Dr. BIX: ltl Milford, OH 45150 AT&T: (513) 576-2070 "When all else fails, read the directions."