bug-bison
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU bison 1.75b] testsuite.log: 14 failures


From: Paul Eggert
Subject: Re: [GNU bison 1.75b] testsuite.log: 14 failures
Date: Sun, 15 Dec 2002 15:37:39 -0800 (PST)

> Date: Sun, 15 Dec 2002 16:33:41 -0500
> From: Bruce Lilly <address@hidden>
> 
> OK, then there are other places in the documentation (e.g. 3.7.8)
> which need to indicate the difference in calling convention for
> yyerror with %parse-param.

Sorry, I don't understand the "3.7.8" reference.  Sections are often
renumbered.  Perhaps you could submit a patch relative to the latest
bison.texinfo?  It's not necessary to propose new wording; just
indicating where the existing wording is unclear would help.

> > Hmm, perhaps we should add an %error-param.
> 
> Either something like that (with the default in the absence of the
> option being a single arg to yyerror) or increase the release number
> of bison to 2 to indicate the incompatibility with (currently released)
> 1.x versions of bison.

I see no incompatibility with Bison 1.35 (the last "old" version of
Bison), since any grammar that works with Bison 1.35 must lack
%parse-param, so Bison 1.50 and later will still generate C code that
invokes yyerror with just one argument.

If we add %error-param, we will break compatibility with existing
grammars that use %parse-param, since %parse-param is documented as
affecting yyerror too.  However, %parse-param has never been in an
official release (it has only been in test releases), so it's OK to do
this.

We do plan to increment the Bison version number to 2.0 soon, since we
think the changes since 1.35 do deserve a version number upgrade.  The
next official release is planned to be 1.875, to emphasize the
"convergence-to-2.0" that we're hoping for.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]