I finally hit bison's limit and cannot find any easy to remove rules in
the ecpg part of the parser anymore. There may be some in the backend
part, but I'd like to keep those in sync.

For the time being I update my machine to a development snapshot bison
1.49, but that doesn't look like a good solution. After all it hasn't
been released yet. 

Since I suppose almost no one of you outthere uses a development version
of bison I cannot commit my changes, or else, you all cannot compile
ecpg anymore. 

So what do we do?

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

Tue, 18 Jun 2002 15:14:01 +0200
Michael Meskes <meskes@postgresql.org>
ECPG won't compile anymore
Michael Meskes <meskes@postgresql.org> writes:
> I finally hit bison's limit and cannot find any easy to remove rules in
> the ecpg part of the parser anymore. There may be some in the backend
> part, but I'd like to keep those in sync.

> So what do we do?

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?

			regards, tom lane

Tue, 18 Jun 2002 10:29:10 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: ECPG won't compile anymore 
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.

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

Tue, 18 Jun 2002 17:09:43 +0200
Michael Meskes <meskes@postgresql.org>
Re: ECPG won't compile anymore
Michael Meskes <meskes@postgresql.org> writes:
> 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. 

That would be trouble, but considering that we are not even thinking of
going beta before late August, is it really a realistic risk?  bison
seems to be making releases quite frequently lately.  They were at 1.30
back in November, according to my archives, so that's 19 releases in the
last 8 months.

If we get to August and there's no official release of bison with the
larger table size, then it will be time to worry, IMHO.

			regards, tom lane

Tue, 18 Jun 2002 13:57:37 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: 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.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Tue, 18 Jun 2002 14:12:45 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: ECPG won't compile anymore
On Tue, Jun 18, 2002 at 01:57:37PM -0400, Tom Lane wrote:
> That would be trouble, but considering that we are not even thinking of
> going beta before late August, is it really a realistic risk?  bison

Yes. After all it's much easier to sync the two if I get smaller
changes. 

> seems to be making releases quite frequently lately.  They were at 1.30
> back in November, according to my archives, so that's 19 releases in the
> last 8 months.

True. But most of them are not for releases. I have no idea which vesion
number will be the one they release. Up to 1.35 they released
frequently, but then it stopped and 1.49 is quite far from 1.35.

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

Wed, 19 Jun 2002 09:34:20 +0200
Michael Meskes <meskes@postgresql.org>
Re: ECPG won't compile anymore
On Tue, Jun 18, 2002 at 02:12:45PM -0400, Bruce Momjian wrote:
> Are we the only ones up against this problem?  Hard to imagine we are

No, there are more, that's why bison is worked on.

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

Wed, 19 Jun 2002 09:35:25 +0200
Michael Meskes <meskes@postgresql.org>
Re: ECPG won't compile anymore
Michael Meskes wrote:
> On Tue, Jun 18, 2002 at 02:12:45PM -0400, Bruce Momjian wrote:
> > Are we the only ones up against this problem?  Hard to imagine we are
> 
> No, there are more, that's why bison is worked on.

All I can say is that I am making incremental commits to gram.y, so you
can ignore the reformatting commits and focus on the ones that affect
your grammar.  Not sure what else can be done.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Wed, 19 Jun 2002 11:50:09 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: ECPG won't compile anymore