Return value of malloc(0)
hnazfoo at googlemail.com
Fri Jun 30 04:58:40 UTC 2006
On Thu, Jun 29, 2006 at 07:29:16PM +0200, Matthias Andree wrote:
> No, sir. Operator precedence: assign first, and then compare, thus the
> comparison will always be true (else you'd be comparing to undefined
> values, which isn't any better). You might as well write:
> foo = malloc(0);
> /* make noise */
Ok, just for having it done:
if (foo == (foo = some_val))
.. would be right to check if foo stayed the same. No?
> There is no way to see a 0x800 return from malloc(0) as "error".
So noone should actually use malloc(0) and check the size_t argument before
passing it, I guess.
One must still have chaos in oneself to be able to give
a birth to a dancing star.
More information about the freebsd-hackers