| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-10-31 01:34:16 | Re: Strange query behavior where clause produces odd behavior on '>' query |
| Previous Message | Jason Long | 2008-10-31 01:29:24 | Re: Decreasing WAL size effects |