| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(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:50:31 |
| Message-ID: | 1297954231.2226.1209.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Thu, 2011-02-17 at 14:37 +0000, Peter Geoghegan wrote:
> 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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-02-17 15:06:15 | Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. |
| Previous Message | Peter Geoghegan | 2011-02-17 14:37:39 | Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-02-17 15:06:15 | Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. |
| Previous Message | Peter Geoghegan | 2011-02-17 14:37:39 | Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit. |