On Tue, 2005-12-06 at 00:55 -0500, Chris Shoemaker wrote: > In the gcc ML thread where the -Wstrict-null-sentinel warning was > added, it was claimed that at least some versions of HPUX and Solaris > 2.8 on 64-bit machines #define NULL 0.
Then those system headers are wrong, not the code that uses NULL as a (void *)0. I wonder if there's a way to use 'typeof()' to get a readout as to whether it needs to be redefined properly? I don't get how C++ can get away with calling NULL == 0 rather than == (void *)0. -- Karl Hegbloom <[EMAIL PROTECTED]> _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
