| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, 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:28:51 |
| Message-ID: | 4D5D5AD3.8080708@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 02/17/2011 12:19 PM, Tom Lane wrote:
> "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.
>
>
Ugh. Isn't there some sort of pragma or similar we can use to shut it up?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-02-17 17:37:43 | pgsql: In documentation example, use concat_values() instead of concat( |
| Previous Message | Tom Lane | 2011-02-17 17:23:14 | Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Eder | 2011-02-17 17:31:04 | Re: Fwd: [JDBC] Weird issues when reading UDT from stored function |
| Previous Message | Andrew Dunstan | 2011-02-17 17:26:55 | Re: Debian readline/libedit breakage |