🚀 go-pugleaf

In article <19281@watdragon.waterloo.edu>,
     achowe@tiger.waterloo.edu (anthony howe) writes ... 

>
>I'm making use of realloc() from the Dale's dlibs. However I wonder
>how close this function is to a standard unix site. In Dale's version
>if <addr> is NULL then a malloc is done. If <size> is zero then a
>free is done. Else resized and possibly moved block of memory.
>NULL may be returned is the block can not be resized.
>
>Now the man page for realloc() here at U(W) does not say anything
>except that the block is resized and possibly moved and that NULL
>may be returned if the resize fails.
>

Dale's version is in accord with the interpretation of the draft ANSI
standard described in "C: A Reference Manual," Harbison and Steele, Tartan
Laboratories (Prentice-Hall), second edition.

char *realloc(ptr,size)
	char *ptr;
	unsigned size; 

"If the first argument to realloc is a null pointer then the function
behaves like malloc .... if ptr is not null and size is zero, realloc
returns a null pointer and the old region is deallocated."

I recommend the book. It's the "other C bible," along with K&R.

-- 
   Steve Yelvington at the (frozen enough to skate!) lake in Minnesota
   UUCP: ... pwcs.StPaul.GOV!stag!thelake!steve