🚀 go-pugleaf

Hi,

This may not be a bug, but ignorance on my part, so please forgive!!

I am using gcc version 2.5.7.   In one of my calls to realloc, the first
parameter happened to be NULL.   As far as I can tell, a program compiled
with gcc will always return NULL from this call.  According to the 3 different
C books I have, when the first parameter is NULL, it should basically 
behave as malloc, i.e. allocate the memory requested if possible.  A simple
program trying to only allocate 1 byte always fails if the first parameter
is NULL (but malloc'ing works).  Is there a newer version of gcc that
fixes this problem?  With every other compiler I try (on the PC as well as
UNIX) I am able to get the memory, but I'd much rather use gcc!!   

I do have a work-around..."myrealloc" which checks the first parameter, if
NULL calls malloc, else calls realloc....


Thanks!
Melissa