Hi,

At Thu, 16 Jan 2003 21:22:01 +0900,
Michal Rokos wrote:
> >>>What about ((void)0) ?
> >>
> >>	Again - gcc warns about 'code has no effect'...
> > I've used this (void)0 trick many times, we have to replace
> > them all to make gcc 3.2.2 quiet?
> > Anyhow, what it defines assert() in <assert.h> if NDEBUG?
> 
> 	You're right - as usually :))

Possibly, gcc 3.2.2 always complains about assert() if NDEBUG?

-- 
Nobu Nakada