Date: Mon, 14 Jan 2013 18:17:47 +0100 From: Igmar Palsenberg <igmar@...senberg.com> To: "musl@...ts.openwall.com" <musl@...ts.openwall.com> Subject: malloc(0) behaviour Hi, Is there a (good) reason for Musl to follow glibc's malloc(0) behaviour ? Musl returns a valid pointer, which is fine according to the standard, but returning NULL is also fine. IMHO, returning NULL is better : It usually kills the program if actual storage is attempted. You also can't do that if a valid pointer is returned, so I really can't grasp the reason for returning a pointer at all, except to support buggy and lazy programming. I suggest we make malloc(0) return a NULL pointer. Any objections ? Regards, Igmar
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.