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

From: Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.
Date: 2011-02-17 14:37:39
Message-ID: AANLkTik0YoGKYyhqkVXeVjMdNEJ3GPF+a8VUynqHteut@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 17 February 2011 08:30, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2011-02-17 14:50:31 Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.
Previous Message Robert Haas 2011-02-17 13:08:45 Re: pgsql: Remove rule to build sepgsql-regtest.pp.

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-02-17 14:50:31 Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.
Previous Message Peter Eisentraut 2011-02-17 14:02:57 Re: why two dashes in extension load files