Re: gcc 4.6 -Wunused-but-set-variable - Mailing list pgsql-hackers

From Tom Lane
Subject Re: gcc 4.6 -Wunused-but-set-variable
Date
Msg-id 9895.1308180533@sss.pgh.pa.us
Whole thread Raw
In response to gcc 4.6 -Wunused-but-set-variable  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: gcc 4.6 -Wunused-but-set-variable
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> I couldn't see a way good way of programming around this (perhaps in the
> second case, but it would get uselessly ugly), so perhaps just marking
> the variables as potentially unused would be appropriate?  See patch.

Of course this would break not only on non-gcc compilers, but old
versions of gcc.  I'd suggest a macro (cf PERL_UNUSED_DECL) and some
version checks at the site of the macro declaration (perhaps the ones
emitted by bison for its use of this construct will do).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Strict Set Returning Functions
Next
From: Tom Lane
Date:
Subject: Re: creating CHECK constraints as NOT VALID