[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: Requiring the ending `;'
From: |
Hans Aberg |
Subject: |
Re: RFC: Requiring the ending `;' |
Date: |
Mon, 4 Mar 2002 20:18:36 +0100 |
At 19:08 +0100 2002/03/04, Akim Demaille wrote:
>>> And in the future, with more algorithms implemented, the
>>> implementation of %expect will not change. What might change is
>>> the number of conflicts.
>
>Hans> Specifically, the same input may produce different parsing
>Hans> results with different algorithms (i.e., the languages parsed
>Hans> becomes different). Or do you have a proof, showing the
>Hans> opposite? :-)
>
>Certainly not, since that's what I say.
I think we have lost the thread to the original discussion:
When changing algorithm (or yacc implementation, if POSIX had not been
specifying LALR(1)), one wants that the same input should parse the same
language, which does not work when using %expect.
The Bison manual treats %expect as a perfectly normal way to handle grammar
ambiguities: This is only OK when one is presumes that the same algorithm
will be used.
Hans Aberg
- Re: RFC: Requiring the ending `;', (continued)
- Re: RFC: Requiring the ending `;', Akim Demaille, 2002/03/03
- Re: RFC: Requiring the ending `;', Hans Aberg, 2002/03/03
- Re: RFC: Requiring the ending `;', Paul Eggert, 2002/03/03
- Re: RFC: Requiring the ending `;', Akim Demaille, 2002/03/03
- Re: RFC: Requiring the ending `;', Hans Aberg, 2002/03/04
- Re: RFC: Requiring the ending `;', Akim Demaille, 2002/03/04
- Re: RFC: Requiring the ending `;', Hans Aberg, 2002/03/04
- Re: RFC: Requiring the ending `;', Akim Demaille, 2002/03/04
- Re: RFC: Requiring the ending `;',
Hans Aberg <=
Re: RFC: Requiring the ending `;', Akim Demaille, 2002/03/03