Re: [HACKERS] parser changes

From: Michael Meskes <meskes(at)postgreSQL(dot)org>
To: PostgreSQL Hacker <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] parser changes
Date: 2000-02-16 07:12:04
Message-ID: 20000216081204.A1592@fam-meskes.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 16, 2000 at 01:26:22AM -0500, Tom Lane wrote:
> >> Do you have a pretty good way to track changes in gram.y? Let me know
> >> if you want some help (though I won't be able to for a week or so).

Right now I'm up-to-date. But I have yet to finish my own todo for 7.0.

> > I told him to keep a copy of the gram.y he uses, and merge changes from
> > the current version against the copy he has that matched the current
> > ecpg.

That's exactly how I do it. I run diff from time to tim and add the changes
to my version by hand.

> It seems to me that this whole business of tracking a hand-maintained
> modified copy of gram.y is wrong. There ought to be a way for ecpg to
> just incorporate the backend grammar by reference, plus a few rules
> on top for ecpg-specific constructs.

I would love this. But frankly I don't see how we can accomblish this. After
all ECPG has to print out the statment word by word while the backend puts
it into internal structure.

> It's probably too late to do anything in this line for 7.0, but
> I suggest we think about it for future releases.

Any ideas anyone?

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(at)Fam-Meskes(dot)De | Use PostgreSQL!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2000-02-16 07:14:22 Re: [HACKERS] function question yet again
Previous Message Hannu Krosing 2000-02-16 06:44:15 Re: [HACKERS] IBM sues Informix over DB patents