Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You're right, in the standard it's implementation-defined. I mistakenly thought malloc(0) was undefined. That said, it's probably not the best-tested code path in the system library.


And correspondingly calling free() on the returned value is also unlikely to be particularly well tested.


Well, unless it's NULL. I'm pretty sure that people call free(0) a lot.


I mean, these are literally all special values that are explicitly called out in all the relevant standards (both ISO C and POSIX). Anyone who is competent and is writing tests for libc would surely cover that.


Probably malloc(0) is not completely untested, yes. But it's unlikely to be regularly executed by applications.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: