d: remove support for parse.error verbose

Without the history, D should not support this option. Before the
removal, 'detailed' and 'verbose' options generated the same code.

* data/skeletons/lalr1.d: Here.
* doc/bison.texi: Adapt tests to use 'detailed' instead of 'verbose'.
* tests/calc.at: Document it.
This commit is contained in:
Adela Vais
2021-01-07 13:39:43 +02:00
committed by Akim Demaille
parent f859462658
commit c13b3c02d3
5 changed files with 13 additions and 14 deletions

View File

@@ -690,7 +690,7 @@ m4_popdef([b4_at_dollar])])dnl
{]b4_parse_error_bmatch(
[custom], [[
yylexer.reportSyntaxError(yyctx);]],
[detailed\|verbose], [[
[detailed], [[
if (yyctx.getToken() != ]b4_symbol(empty, kind)[)
{
// FIXME: This method of building the message is not compatible
@@ -732,7 +732,7 @@ m4_popdef([b4_at_dollar])])dnl
}
]b4_parse_error_bmatch(
[detailed\|verbose], [[
[detailed], [[
private int yysyntaxErrorArguments(Context yyctx, SymbolKind[] yyarg, int yyargn) {
/* There are many possibilities here to consider:
- If this state is a consistent state with a default action,