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

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 16:38:49
Message-ID: 4D5CFAB9020000250003AB9F@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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).

-Kevin

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Kevin Grittner 2011-02-17 17:07:09 Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.
Previous Message Tom Lane 2011-02-17 16:26:35 Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2011-02-17 16:41:37 Re: Debian readline/libedit breakage
Previous Message Stephen Frost 2011-02-17 16:28:19 Re: Debian readline/libedit breakage