Re: Is it really such a good thing for newNode() to be a macro?

Tom Lane wrote:
> I considered that one, but since part of my argument is that inlining
> this is a waste of code space, it seems like a better inlining
> technology isn't really the answer.

The compiler presumably has the intelligence and the command-line options to 
control how much inlining one wants to do.  But without any size vs. 
performance measurements it is an idle discussion.  Getting rid of a global 
variable and macro ugliness is a worthwhile goal of its own.