Sam Steingold <[EMAIL PROTECTED]> writes:

> this is the standard way to handle calloc/malloc/alloca.

It's one standard way, but there are others.  In C, generally it's
better to avoid the casts, since casts can suppress useful
diagnostics.  So, in C, it's usually better to not cast the results of
malloc.  So there is a tradeoff here between g++ compatibility (a good
thing) and C source code reliability (another good thing).

This casting business is a relatively minor point; I'm more worried
about the old-style function definitions.  I wish I knew why glibc
does it that way.


Reply via email to