This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: cp/parse.y:2120: invalid value: $3
- From: "David O'Brien" <obrien at NUXI dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Paul Eggert <eggert at twinsun dot com>, "jakub at redhat dot com" <jakub at redhat dot com>, "davem at redhat dot com" <davem at redhat dot com>, "nathan at cs dot bris dot ac dot uk" <nathan at cs dot bris dot ac dot uk>, "bug-gcc at gnu dot org" <bug-gcc at gnu dot org>, "bug-bison at gnu dot org" <bug-bison at gnu dot org>
- Date: Tue, 30 Apr 2002 18:34:28 -0700
- Subject: Re: cp/parse.y:2120: invalid value: $3
- Organization: The NUXI BSD group
- References: <200204292322.g3TNM0R00942@shade.twinsun.com> <9020000.1020125193@warlock.codesourcery.com>
- Reply-to: obrien at NUXI dot com
On Mon, Apr 29, 2002 at 05:06:33PM -0700, Mark Mitchell wrote:
> > 2002-04-29 Paul Eggert <eggert@twinsun.com>
> >
> > * parse.y (nomods_initdcl0): Do not move stack entries
> > when setting things up as initdcl0_innards expects.
> > This avoids a typo caught by CVS Bison; let's buy Akim
> > Demaille a beer!
>
> Nathan, would you apply this patch to branch and mainline, please?
> (Leave out the last two lines of the ChangeLog entry; we'll stick to
> the facts.)
Thank you.
My responce to reading that ChangeLog was:
Feh! Lets buy Robert Corbett and the CSRG a beer. Berkeley YACC
from 4.4BSD reported this bug long before Bison did.
[I wasn't going to respond to this thread publicly, but give credit where
credit is due].
This just shows why just because a single tool "works", people should not
ignore the real diagnosttics from another tool.
I did not like the C output especially compaired to what Byacc did the
face of the error. However I was so put down when I brought up there was
an error in the grammar I didn't bother to send the C code differences to
this list as I wasn't being listened to.