glr2.cc: don't use YYSTYPE/YYLTYPE at all

* data/skeletons/glr2.cc: Define value_type and location_type where
needed, and use them only.
(yyuserMerge): Make it a member function of the glr_state class.
This commit is contained in:
Akim Demaille
2020-12-26 09:13:59 +01:00
parent 8db99c54f4
commit d0e44162b5
2 changed files with 52 additions and 72 deletions

4
TODO
View File

@@ -211,10 +211,6 @@ Some occurrences were fixed, but now some have improper names:
yycharp is no longer a Pointer. And yystackp should probably also be a reference.
*** Use proper type names
Don't use YYSTYPE and YYLTYPE but parser::semantic_type and
parser::location_type. Undefine YYSTYPE and YYLTYPE.
*** parse.assert
Currently all the assertions are enabled. Once we are confident in glr2.cc,
let parse.assert use the same approach as in lalr1.cc.