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

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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
Subject: Re: Is it really such a good thing for newNode() to be a macro?
Date: 2008-08-27 15:36:02
Message-ID: 200808271836.03221.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

In response to

Responses

pgsql-hackers by date

Next:From: Greg StarkDate: 2008-08-27 15:45:27
Subject: Re: Is it really such a good thing for newNode() to be a macro?
Previous:From: Heikki LinnakangasDate: 2008-08-27 15:05:38
Subject: Re: Is it really such a good thing for newNode() to be a macro?

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