On Wed, Feb 16, 2000 at 10:07:06AM -0500, Tom Lane wrote:
> ...
> Aside from the work involved, the major problem with any of these
> approaches is that practically any change in or around the backend's
> gram.y would instantly break ecpg; backend and ecpg source would
That means everyone who changes gram.y nowadays would then have to change
the corresponding ecpg function as well. Nice idea. :-)
> there will be much enthusiasm for it among the backend developers.
I'm afraid you're right on this one.
> Still, it seems like you might want to think about building some
> kind of tool to help you with keeping the files in sync. For example,
> it'd probably be easier to diff ecpg and backend grammar files if
> you made a script that just strips out the action parts.
It's not that difficult to read and apply a context diff by hand. After all
the changes are mostly moderately.
michael
--
Michael Meskes | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz | Go Rhein Fire!
Tel.: (+49) 2431/72651 | Use Debian GNU/Linux!
Email: Michael@Fam-Meskes.De | Use PostgreSQL!