From: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Michael Meskes" <meskes(at)postgresql(dot)org> |
Cc: | "PostgreSQL Hacker" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ECPG won't compile anymore |
Date: | 2002-06-18 20:50:50 |
Message-ID: | D90A5A6C612A39408103E6ECDD77B82920CF7B@voyager.corporate.connx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
> Sent: Tuesday, June 18, 2002 11:13 AM
> To: Michael Meskes
> Cc: PostgreSQL Hacker
> Subject: Re: [HACKERS] ECPG won't compile anymore
>
>
> Michael Meskes wrote:
> > On Tue, Jun 18, 2002 at 10:29:10AM -0400, Tom Lane wrote:
> > > I'd be inclined to say that you don't commit until bison 1.49 is
> > > officially released. Got any idea when that will be?
> >
> > No, that's the problem. ECPG and the backend parser are
> running out of
> > sync. After all bison's release may be later than our next one.
> >
> > I cannot commit even simple bugfixes anymore as my source tree
> > already has the uncompilable bison file. So I would have to
> work on two
> > different source trees. I don't exactly like that.
>
> Are we the only ones up against this problem? Hard to imagine we are
> the only ones up against this limit in bison. Are there
> other options?
> I don't see how we can distribute ecpg in 7.3 without some
> kind of fix.
There are some other freely available parser/generators. I like the
Lemmon parser generator. Of course, I have no idea how traumatic it
would be to convert a Bison grammar into Lemmon. There is also PCCTS
and some other free ones.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-06-18 20:53:16 | Re: PostgreSQL SQL92: CORRESPONDING BY |
Previous Message | Marek Mosiewicz | 2002-06-18 20:50:16 | Re: Roadmap for a Win32 port |