Re: hint infrastructure setup (v3)

Fabien COELHO wrote:
> I would not like to break postgresql portability with other parser
> generators. It would be enough to reject the patch from my point of
> view;-)

We require bison to build, period. I am sure we use enough
bison-specific stuff now. No one has suggested another parser generator
to support either.

>
> Using some non standard undocumented API would not help other people who
> would like to touch the parser.
>
> It would not help me either, because I would have to learn the
> undocumented API;-)
>
> I really need to give a name to the state so as to be able to attach a
> hint. I cannot set how I could guess the state number given after "GRANT"
> just from the source, and without generating lots of conflicts.
>
> So I'll do some more programming maybe over the week-end a resubmit
> something soon.

Please show us an example of what a typical hint would look like to the
user.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073