[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MAXTABLE & Serious issues with bison 1.30
From: |
Akim Demaille |
Subject: |
Re: MAXTABLE & Serious issues with bison 1.30 |
Date: |
03 Jan 2002 11:02:48 +0100 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) |
>>>>> "Tim" == Tim Van Holder <address@hidden> writes:
>> Happy new year.
Tim> Best wishes to you and yours as well.
Thanks!
>> This is something upon which we will all agree. First of all, what
>> is the exact limit you're hitting?
Tim> I didn't expirment to find out the actual size used; doubling the
Tim> existing limit seemed acceptable (in fact, I think the existing
Tim> limit was only chosen for memory conservation reasons, as a lower
Tim> limit is used for the real-mode DOS version; those issues hardly
Tim> matter these days (especially since we're talking about less than
Tim> 1MB)).
Sorry, I was pretty unclear: I meant what Bison limit is hit? Number
of rules, number of items, number of symbols, number of gotos etc.
But you seem to have given a grammar, I'll have a look myself, thanks!
>> 1.30 is dead broken.
Tim> I noticed.
:)
Tim> Sure. I'm told it is GPL'd, so I can distribute it. I've
Tim> attached it to this message.
Thanks!
Tim> It's not the cleanest grammar by a long shot (1060+681 conflicts,
Tim> most of which were probably caused by stripping the actions), but
Tim> that shouldn't matter to bison.
No kidding!!! Yahoo!
Tim> as bison has no relation to autoconf.
>> Yes, it has: me.
Tim> Well yes - but I meant bison as a program, not the bison
Tim> project.
Man, I know, I was teasing :)
Tim> I don't mind if bison _uses_ a prerelease version, but then the
Tim> generated files should also be in CVS.
Again, this is what I would have done had exp needed exp, but it is
not the case, it uses 1.31. We agree.
Tim> Then the configure script for the trunk should check for a
Tim> compatible version of bison and complain if it's not found.
You sure have some spare time Tim :) Be my guest.