Re: Warnings in compile - Mailing list pgsql-hackers

From Michael Meskes
Subject Re: Warnings in compile
Date
Msg-id 20090525170207.GA5764@feivel.credativ.lan
Whole thread Raw
In response to Re: Warnings in compile  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Warnings in compile  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, May 25, 2009 at 12:10:49PM -0400, Tom Lane wrote:
> Consider
> 
>     if (...)
>         macro;
>     else
>         something-else;
> ...

Sure, but some/most/all macros are called as 

MACRO;

No real reason there it seems.

> [ 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)

Will try, but probably not now. :-)

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@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: [PATCH] cleanup hashindex for pg_migrator hashindex compat mode (for 8.4)
Next
From: "Kolb, Harald (NSN - DE/Munich)"
Date:
Subject: Re: Synchronous replication: Promotion of Standby to Primary