gnugo-devel
[Top][All Lists]
Advanced

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

Re: [gnugo-devel] Re: Stack over-run


From: Dave Denholm
Subject: Re: [gnugo-devel] Re: Stack over-run
Date: 19 Feb 2002 18:01:46 +0000

Daniel Bump <address@hidden> writes:

> Gunnar wrote:
> 
> > Trevor wrote:
> > > Unfortunately, this idiom doesn't work for the TRACE family.
> > > The variable argument list can't be passed in.  That is, there
> > > is no way to put the "} while (0)" part after the argument
> > > list (unless you have variadic macros).
> > 
> > Right, I forgot about the limitations in this context. The solution
> > 
> > +#define TRACE  (verbose) && gprintf
> > 
> > in your patch looks good enough.
> 
> This appears to work correctly but generates a lot of
> warnings with GCC.
> 
> worm.c: In function `make_worms':
> worm.c:228: warning: value computed is not used
> worm.c:300: warning: value computed is not used
> worm.c:338: warning: value computed is not used
> 

Sorry, haven't been watching this thread...

if it's only gcc that's giving these warnings, then can
gcc builds use variadic macros, and then only non-gcc
will see the alternate formulations of TRACE() ..?


dd
-- 
address@hidden          http://www.insignia.com



reply via email to

[Prev in Thread] Current Thread [Next in Thread]