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: Bruce Lilly
Subject: Re: [GNU bison 1.75b] testsuite.log: 14 failures
Date: Sun, 15 Dec 2002 19:36:13 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

Paul Eggert wrote:
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.

That's the section number I get via make bison.pdf in doc.
It's titled "A Pure (Reentrant) Parser" and the first paragrah's first
sentence begins with "A reentrant program is one which does not alter
in the course of execution".  The section has a reference to yyerror
but makes no mention of a change in calling convention for yyerror.

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.

Certainly 1.33 and IIRC earlier versions had the ability to generate
reentrant parsers (though with a mechanism different than a %-option)
with additional parameters but with no change to the yyerror calling
convention.  Indeed, the mechanisms used in those versions still appear
to work with 1.75b in lieu of %parse-param (which is incompatible with
earlier versions of bison).










reply via email to

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