Michael Meskes <meskes@postgresql.org> writes:
> I recently (on my flight to Ottawa) changed ecpg to use the keyword list
> of the backend instead of its own. This means that there is one less
> file to sync manually. However, it also means that an additional keyword
> defined in the backend will break compilation as ecpg doesn't have this
> definition in its parser.
> Does anyone object to moving the symbol definition part to a file of its
> own that's inluded by both parser? Or does anyone have a better idea?
AFAIK bison doesn't have an "include" capability, so I'm not sure how
you plan to make that work?
regards, tom lane
