malloc(0)

Roland McGrath roland@frob.com
Mon Jun 1 10:54:00 GMT 1998


My recollection is that we made it that way quite a long time ago because
existing programs assumed that behavior (malloc(0) != 0).  You have cited
no advantage whatsoever in changing it.



More information about the Libc-hacker mailing list