| Subject: | Re: Is it really such a good thing for newNode() to be a macro? |
|---|---|
| From: | Tom Lane |
| Date: | Sat, 30 Aug 2008 11:51:49 -0400 |
| Newsgroups: | pgsql.hackers |
"Stephen R. van den Berg" <srb@xxxxxxx> 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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
|
| Previous by Date: | Re: Is it really such a good thing for newNode() to be a macro?, "Stephen R. van den Berg" |
|---|---|
| Next by Date: | Attaching error cursor position to invalid constant values, Tom Lane |
| Previous by Thread: | Re: Is it really such a good thing for newNode() to be a macro?, "Stephen R. van den Berg" |
| Next by Thread: | Re: Is it really such a good thing for newNode() to be a macro?, "Alex Hunsaker" |
| Indexes: | [Date] [Thread] [Top] [All Lists] |