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

From Simon Riggs
Subject Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.
Date
Msg-id 1297954231.2226.1209.camel@ebony
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.  (Peter Geoghegan <peter.geoghegan86@gmail.com>)
Responses Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, 2011-02-17 at 14:37 +0000, Peter Geoghegan wrote:
> On 17 February 2011 08:30, Simon Riggs <simon@2ndquadrant.com> wrote:
> > In file included from gram.y:12758:
> > scan.c: In function ‘yy_try_NUL_trans’:
> > scan.c:16256: warning: unused variable ‘yyg’
> 
> Lots of people have reported that one. It's been around since August
> of last year, if not earlier.

Yeh. I wasn't reporting it as an error, just showing the absence of a
warning for an uninitialized variable in the case shown.

What I should have said was: please share any tips for improving error
checking.

-- Simon Riggs           http://www.2ndQuadrant.com/books/PostgreSQL Development, 24x7 Support, Training and Services



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.
Next
From: Robert Haas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.