In message: <[EMAIL PROTECTED]> Marc Recht <[EMAIL PROTECTED]> writes: : A malloc(0) returns always 0x800 on my system. This causes some third-party : software to fail, because they expect malloc(0) to return NULL. Is this a : bug or a feature? malloc(3) doesn't mention anything.
malloc(0) is undefined. If people expect it to return NULL, that software is not standard conforming. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
