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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Is it really such a good thing for newNode() to be a macro?
Date: 2008-08-30 15:51:49
Message-ID: 21773.1220111509@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Stephen R. van den Berg" <srb(at)cuci(dot)nl> writes:
> Tom Lane wrote:
>> ({	Node   *__result__; \

> Please avoid identifiers starting with __ .

Yeah, I had misremembered which way that rule went.  It's "_result"
as committed.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-08-30 20:18:57
Subject: Attaching error cursor position to invalid constant values
Previous:From: Stephen R. van den BergDate: 2008-08-30 10:02:40
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