Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-09 12:23:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

c++: remove the yy prefix from some functions

Browse Source 
yy::parser features a parse() function, not a yyparse() one.

* data/skeletons/lalr1.cc (yyreport_syntax_error)
(context::yyexpected_tokens): Rename as...
(report_syntax_error, context::expected_tokens): these.
This commit is contained in:
Akim Demaille
2020-04-12 08:14:12 +02:00
parent e50de09886
commit ecf5cb7e0e
3 changed files with 8 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
TODO
View File

@@ -1,20 +1,11 @@
* Bison 3.6
** C++
yyreport_syntax_error should always be the name of the reporting, yyparse
should not have to dispatch to several APIs.
** Documentation
- yyexpected_tokens in all the languages.
- yyexpected_tokens/expected_tokens/expectedTokens in all the languages.
- YYENOMEM
- YYERRCODE, YYUNDEF, YYEOF
- i18n in Java
- symbol.type_get should be kind_get, and it's not documented.
** Naming conventions
There's no good reason to use the "yy" prefix in parser::context, is there?
See also the case of Java. We should keep the prefix for private
implementation details, but maybe not for public APIs.
** User token number, internal symbol number, external token number, etc.
There is some confusion over these terms, which is even a problem for
translators. We need something clear, especially if we provide access to