Xref: utzoo comp.std.c:967 comp.lang.c:17306
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!decwrl!megatest!djones
From: djones@megatest.UUCP (Dave Jones)
Newsgroups: comp.std.c,comp.lang.c
Subject: Re: realloc
Message-ID: <3229@goofy.megatest.UUCP>
Date: 30 Mar 89 23:14:01 GMT
References: <681@sdrc.UUCP>
Organization: Megatest Corporation, San Jose, Ca
Lines: 19

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


Gack.

The realloc((char*)0, size) thing was bad enough. What's this all
about?

Stuff like this just makes it hard to port ANSII programs to
old systems. Also makes it harder to convert an old system to ANSII.
I can't think of any good reason to add such a silly spec. What am I
missing?

Can anyone suggest a legitimate reason why they would want to do such
a thing?