Re: Scanner/Parser question - what does _P imply? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Scanner/Parser question - what does _P imply?
Date
Msg-id 27181.1169134508@sss.pgh.pa.us
Whole thread Raw
In response to Scanner/Parser question - what does _P imply?  (<korryd@enterprisedb.com>)
Responses Re: Scanner/Parser question - what does _P imply?  (<korryd@enterprisedb.com>)
Re: Scanner/Parser question - what does _P imply?  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
<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.
        regards, tom lane


pgsql-hackers by date:

Previous
From:
Date:
Subject: Scanner/Parser question - what does _P imply?
Next
From: Richard Huxton
Date:
Subject: Re: Temparary disable constraint