| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. |
| Date: | 2011-02-17 17:19:48 |
| Message-ID: | 10348.1297963188@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-02-17 17:23:14 | Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. |
| Previous Message | Kevin Grittner | 2011-02-17 17:07:09 | Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-02-17 17:23:14 | Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. |
| Previous Message | Tom Lane | 2011-02-17 17:16:56 | Re: contrib loose ends: 9.0 to 9.1 incompatibilities |