Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.
Date
Msg-id 10348.1297963188@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
"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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: contrib loose ends: 9.0 to 9.1 incompatibilities
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.