[15704] in Kerberos_V5_Development
Re: calloc/malloc return value checking
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Apr 23 13:09:49 2010
From: Greg Hudson <ghudson@mit.edu>
To: Jeff Blaine <jblaine@kickflop.net>
In-Reply-To: <4BD19A9B.30900@kickflop.net>
Date: Fri, 23 Apr 2010 11:26:02 -0400
Message-ID: <1272036362.19726.102.camel@ray>
Mime-Version: 1.0
Cc: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Fri, 2010-04-23 at 09:03 -0400, Jeff Blaine wrote:
> Just throwing this out there out of curiosity (learning).
>
> I'm seeing a lot of MIT krb5 code using:
>
> blah = malloc(...); /* or calloc() */
> if (blah == 0)
>
> Is there an aversion to 'NULL' for some reason?
NULL is currently preferred, per:
http://k5wiki.kerberos.org/wiki/Coding_style/Practices#The_many_names_of_zero
We have an old code base which didn't have strong coding standards for
most of its lifetime; there was likely a developer or two who didn't
like using NULL.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
