[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bug in bison 1.875
From: |
Paul Eggert |
Subject: |
Re: bug in bison 1.875 |
Date: |
03 Mar 2003 13:51:22 -0800 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) Emacs/20.3 |
Martin MOKREJŠ <address@hidden> writes:
> > I'd prefer a solution that actually reflects the problem, not some
> > arbitrary thing like a version number
>
> But the bug really is in the compiler.
The bug may happen in the same compiler with other version number, or
in other seemingly-unrelated compilers with entirely different version
numbers. If the bug is common enough for us to be worried about, we
should test for its presence instead of looking for a particular
compiler name and version number (which would be a neverending task to
keep track of).
It's also conceivable that there is a bug in Bison, not your compiler.
For example, the bug might be a portability problem, which is
manifested on your implementation (with some combination of
compile-time options) but not on other implementations. If so, we
should fix the Bison bug.
- Re: bug in bison 1.875, Paul Eggert, 2003/03/01
- Re: bug in bison 1.875, Martin MOKREJŠ, 2003/03/02
- Re: bug in bison 1.875,
Paul Eggert <=
- Re: bug in bison 1.875, Martin MOKREJŠ, 2003/03/04
- Re: bug in bison 1.875, Paul Eggert, 2003/03/04
- Re: bug in bison 1.875, Martin MOKREJŠ, 2003/03/04
- Re: bug in bison 1.875, Paul Eggert, 2003/03/04
- Re: bug in bison 1.875, Martin MOKREJŠ, 2003/03/05
- Re: bug in bison 1.875, Martin MOKREJŠ, 2003/03/11
- Re: bug in bison 1.875, Paul Eggert, 2003/03/11
- Message not available
- Re: bug in bison 1.875, Paul Eggert, 2003/03/11
- Re: bug in bison 1.875, Martin MOKREJŠ, 2003/03/12
- Re: bug in bison 1.875, Martin MOKREJŠ, 2003/03/28