|
From: | Akim Demaille |
Subject: | Re: RFC: %param |
Date: | Wed, 9 Sep 2009 16:02:20 +0200 |
Hi Paolo,Below is discussed a difference bw the Java parsers and the others. What opinion do you have about it? Do you see a means to converge?
Le 7 sept. 2009 à 09:55, Akim Demaille a écrit :
Hi, I was tired to read%parse-param {::parser::ParserImpl& up} %lex-param {::parser::ParserImpl& up} %parse-param {yyFlexLexer& scanner} %lex-param {yyFlexLexer& scanner}in my code, I wanted%param {::parser::ParserImpl& up}{yyFlexLexer& scanner};I pushed this feature in candidates/%param, but there are several issues:- I had not noticed, but when I started upgrading the documentation, I discovered that in lalr1.java, the %lex-params are added to the signature of yyparse, which in my case would have allowed to use only %lex-params. It makes sense, but I am uncomfortable with the coexistence of several conventions within Bison.
[This is in master, i.e., it will be 2.6. 2.4.2, and 2.5 should be released before hand.]
[Prev in Thread] | Current Thread | [Next in Thread] |