Michael Meskes <mes...@postgresql.org> writes: > On Mon, May 25, 2009 at 11:27:27AM -0400, Tom Lane wrote: >> You can't just remove the "else", or it's unsafe;
> But why? What does this empty else accomplish? Consider if (...) macro; else something-else; Without the "else" in the macro, this code would be parsed in a surprising fashion, ie else bound to the wrong if. I'm afraid that "else {}" might not be any better --- it might fail outright in this context. [ 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) regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers