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

From Peter Geoghegan
Subject Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.
Date
Msg-id AANLkTik0YoGKYyhqkVXeVjMdNEJ3GPF+a8VUynqHteut@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
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.

--
Regards,
Peter Geoghegan


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: why two dashes in extension load files
Next
From: Simon Riggs
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.