Re: Scanner/Parser question - what does _P imply?

Поиск
Список
Период
Сортировка
От Jan Wieck
Тема Re: Scanner/Parser question - what does _P imply?
Дата
Msg-id 45B9071B.9060806@Yahoo.com
обсуждение исходный текст
Ответ на Re: Scanner/Parser question - what does _P imply?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Scanner/Parser question - what does _P imply?  (<korryd@enterprisedb.com>)
Список pgsql-hackers
On 1/18/2007 10:35 AM, Tom Lane wrote:
> <korryd@enterprisedb.com> writes:
>> Many of the keywords listed in keywords.c are defined with symbolic
>> names that end in '_P' (underscore P).
>> What differentiates those keywords from the other keywords?  What does
>> the 'P' stand for?
> 
> P = Parser.  The reason for the _P is just to avoid conflicts with
> other definitions of the macro name, either in our own code or various
> platforms' header files.  We haven't been totally consistent about it,
> but roughly speaking we've stuck _P on when it was either known or
> seemed likely that there might be a conflict.
> 
> Some years ago there was discussion of consistently P-ifying *all* those
> macros, but it didn't get done; I think Thomas or somebody objected that
> it would make gram.y needlessly harder to read.

Are there many people who read gram.y on a regular base?


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: BUG #2917: spi_prepare doesn't accept typename aliases such as 'integer'
Следующее
От:
Дата:
Сообщение: Re: Scanner/Parser question - what does _P imply?