RE: C++ gnome code vs. gcc-2.95.1



> (that is what
> > Stroustrup recommends in his book).
> 
> No, that isn't what Stroupstrup recommends in his book. On 
> the contrary, he notes the possibility of NULL being defined 
> to something other than plain 0, and advises against using 
> NULL--use 0 instead. 

or was it Scott Meyers :)

> Hmm... Can you #undef NULL where you use these macros and 
> define NULL as above?

sure I can, but should I be forced to do it ? Shouldn't the macros
themselves be fixed ?

marcin



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]