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

[Marcin Gorycki <mgo olicom dk>]

> On Wed, 6 Oct 1999, Marcin Gorycki wrote:
> > > 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 ?
> > 
> 
> I don't think 0 is correct in C; that is the problem. Using 0 
> for the NULL
> pointer may cause "implicit conversion from integer to 
> pointer" warnings.

solution:

#ifdef __cplusplus
#undef NULL
#define NULL 0
#endif 

marcin