This is the mail archive of the
libc-alpha@cygnus.com
mailing list for the glibc project.
Re: [Andrew Pimlott <pimlott@abel.MATH.HARVARD.EDU>] realloc(p, 0) vs. free
- To: tb@MIT.EDU (Thomas Bushnell, BSG)
- Subject: Re: [Andrew Pimlott <pimlott@abel.MATH.HARVARD.EDU>] realloc(p, 0) vs. free
- From: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
- Date: Sat, 01 May 1999 11:51:01 -0400
- cc: libc-alpha@cygnus.com
tb@MIT.EDU (Thomas Bushnell, BSG) said:
> Roland McGrath <roland@frob.com> writes:
> > The only thing that is optional is whether malloc(0) returns null or
> > a block that can be freed.
> And let's be clear that while it's permissible under ANSI C for
> malloc(0) to return null, any sane system returns a unique pointer
> that can be freed.
free(NULL) can do exactly nothing, so this is wholy under libc's
control. No sane C program would arbitrarily assume more than ANSI
provides, anyway.
--
Horst von Brand vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Viņa del Mar, Chile +56 32 672616