On Thu, Feb 28, 2013 at 4:09 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > I believe however that it's possible to extract an idea of which > tokens the parser believes it can see next at any given parse state. > (I've seen code for this somewhere on the net, but am too lazy to go > searching for it again right now.) So we could imagine a rule along > the lines of "if IDENT is allowed as a next token, and $KEYWORD is > not, then return IDENT not the keyword's own token". > > This might be unworkable from a speed standpoint, depending on how > expensive it is to make the determination about allowable next symbols. > But it seems worth looking into.
Interesting idea. But wouldn't that change the semantics of the grammar in some places? In particular, keywords would generally become less-reserved than they are now, but in a context-dependent way. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
