On Di, 2014-10-07 at 22:49 +0200, Fabian Frederick wrote: > > > On 07 October 2014 at 22:33 Guenter Roeck <li...@roeck-us.net> wrote: > > > > > > On Tue, Oct 07, 2014 at 04:18:32PM -0400, David Miller wrote: > > > From: Fabian Frederick <f...@skynet.be> > > > Date: Tue, 7 Oct 2014 22:16:36 +0200 > > > > > > > static values are automatically initialized to NULL > > > > > > > > Signed-off-by: Fabian Frederick <f...@skynet.be> > > > > > > Isn't there some implementation room given to compilers > > > as to the representation of true and false? > > > > Not for true/false. > > > > C99 standard, section 7.16: > > > > ... > > The remaining three macros are suitable for use in #if preprocessing > > directives. They are > > > > true > > > > which expands to the integer constant 1, > > > > false > > > > which expands to the integer constant 0, and > > ... > > > > No idea where the NULL comes into the picture, though. > > > > Guenter > > Maybe comment should have been "static values are automatically initialized to > 0" then ?
I think David's concern was whether if 0 == false in all situations. It is pretty clear that static memory is initialized to 0. Thanks, Hannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/