On Fri, Jun 24, 2005 at 09:13:30AM -0500, Andy Lester wrote: > > Initializing x silences the warning. I'm open to other suggestions of > > how to silence it, but I'd like it silenced somehow. > > You and me both. That's why I made it a macro, so that it would work > across all compilers. > > What if you change it in perl.h to: > > #ifndef PERL_UNUSED_VAR > # ifdef __BCC__ > # define PERL_UNUSED_VAR(x) (x)=1 > # else > # define PERL_UNUSED_VAR(x) ((void)x) > # endif > #endif > > Does that make BCC happy?
That's dangerous if x is actually used later on. (x)=0 would be safer, as assigning the integer 1 to pointers will (or at least should) generate an error. Nicholas Clark
