diff options
| author | Akim Demaille <akim.demaille@gmail.com> | 2020-04-12 08:14:12 +0200 |
|---|---|---|
| committer | Akim Demaille <akim.demaille@gmail.com> | 2020-04-12 13:56:44 +0200 |
| commit | ecf5cb7e0e1f7d025dee1e40cf345d5728dab2b2 (patch) | |
| tree | b06fd36b3165c6c12e8db7aa7b8cbe843e66a542 /TODO | |
| parent | e50de09886bfdf4febb75accdd1549952787b5e0 (diff) | |
| download | bison-ecf5cb7e0e1f7d025dee1e40cf345d5728dab2b2.tar.gz | |
c++: remove the yy prefix from some functions
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.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 11 |
1 files changed, 1 insertions, 10 deletions
@@ -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 |