Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.
Дата
Msg-id 4D5D5AD3.8080708@dunslane.net
обсуждение исходный текст
Ответ на Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Список pgsql-hackers

On 02/17/2011 12:19 PM, Tom Lane wrote:
> "Kevin Grittner"<Kevin.Grittner@wicourts.gov>  writes:
>> Tom Lane<tgl@sss.pgh.pa.us>  wrote:
>>> Would you check whether just casting the function result to (void)
>>> shuts it up?
>
>> Casting the result to (void) didn't change the warning.  It shut up
>> when I declared a local variable and assigned the value to it (which
>> was then never used).
> Too bad.  I believe gcc 4.6 will warn about *that*, so it's not going to
> be much of an improvement for long.
>
>             

Ugh. Isn't there some sort of pragma or similar we can use to shut it up?

cheers

andrew


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: Debian readline/libedit breakage
Следующее
От: David Kerr
Дата:
Сообщение: Re: default_tablespace