Skip site navigation (1) Skip section navigation (2)

Re: Sun Studio compiler warnings

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Sun Studio compiler warnings
Date: 2008-10-31 01:34:10
Message-ID: 20081031013409.GO3857@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas escribió:
> > The closing semicolon is strictly speaking not allowed here.  We could
> > remove it, but that would probably upset pgindent?
> >
> > I recall that we used to have a bunch of similar problems with the AIX
> > compilers a long time ago.  Does anyone recall the solution, and do we still
> > care?  (Note that it's only a warning in this case.)
> 
> How about the good old
> 
> do {
> ...
> } while (0)
> 
> trick?

That can't be used because the macro is defining a completely new
function.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-10-31 01:34:16
Subject: Re: Strange query behavior where clause produces odd behavior on '>' query
Previous:From: Jason LongDate: 2008-10-31 01:29:24
Subject: Re: Decreasing WAL size effects

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group