| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Meskes <meskes(at)postgresql(dot)org>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Warnings in compile |
| Date: | 2009-05-29 13:54:26 |
| Message-ID: | 20090529135426.GA18258@feivel.credativ.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 25, 2009 at 12:10:49PM -0400, Tom Lane wrote:
> [ thinks for a bit... ] What might be both safe and warning-free
> is to code an explicit empty statement, viz macro body as
>
> if (1) { ... } else ((void) 0)
I just tried this and yes, it quietens gcc and probably is at least as save as
the old version. Therefore I just commit this small change.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-05-29 14:11:22 | Re: search_path vs extensions |
| Previous Message | Robert Haas | 2009-05-29 13:35:41 | Re: PostgreSQL Developer meeting minutes up |