Re: Sun Studio compiler warnings

From: "Robert Haas" <robertmhaas(at)gmail(dot)com>
To: "Alvaro Herrera" <alvherre(at)commandprompt(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:37:50
Message-ID: 603c8f070810301837s47ee1516l180ac1d2738fe776@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ooooh.... yeah. Time for some caffeine.

...Robert

On Thu, Oct 30, 2008 at 9:34 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> 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

Browse pgsql-hackers by date

  From Date Subject
Next Message Dann Corbit 2008-10-31 01:54:56 Re: Strange query behavior where clause produces odd behavior on '>' query
Previous Message Tom Lane 2008-10-31 01:34:16 Re: Strange query behavior where clause produces odd behavior on '>' query