From: Akim Demaille Date: Wed, 5 Dec 2012 10:03:08 +0000 (+0100) Subject: Merge remote-tracking branch 'origin/maint' X-Git-Tag: v2.7.90~263 X-Git-Url: https://git.saurik.com/bison.git/commitdiff_plain/d6dc4d36d1db744b060029254eaabaaa525a1c19 Merge remote-tracking branch 'origin/maint' * origin/maint: getargs: don't label --language/-l as experimental getargs: fix the locations of command-line input errors: indent missing action code semicolon warning Conflicts: NEWS src/scan-code.l tests/actions.at --- d6dc4d36d1db744b060029254eaabaaa525a1c19 diff --cc NEWS index a1bb0f91,93a1ef54..e9b7fd9b --- a/NEWS +++ b/NEWS @@@ -2,246 -2,11 +2,251 @@@ GNU Bison NEW * Noteworthy changes in release ?.? (????-??-??) [?] +** Incompatible changes + +*** Obsolete features + + Support for YYFAIL is removed (deprecated in Bison 2.4.2). + Support for yystype and yyltype (instead of YYSTYPE and YYLTYPE) + is removed (deprecated in Bison 1.875). + Support for YYPARSE_PARAM is removed (deprecated in Bison 1.875). + +** Warnings + +*** Enhancements of the -Werror option + + The -Werror=CATEGORY option is now recognized, and will treat specified + warnings as errors. The warnings need not have been explicitly activated + using the -W option, this is similar to what GCC 4.7 does. + + For example, given the following command line, Bison will treat both + warnings related to POSIX Yacc incompatibilities and S/R conflicts as + errors (and only those): + + $ bison -Werror=yacc,error=conflicts-sr input.y + + If no categories are specified, -Werror will make all active warnings into + errors. For example, the following line does the same the previous example: + + $ bison -Werror -Wnone -Wyacc -Wconflicts-sr input.y + + (By default -Wconflicts-sr,conflicts-rr,deprecated,other is enabled.) + + Note that the categories in this -Werror option may not be prefixed with + "no-". However, -Wno-error[=CATEGORY] is valid. + + Note that -y enables -Werror=yacc. Therefore it is now possible to require + Yacc-like behavior (e.g., always generate y.tab.c), but to report + incompatibilities as warnings: "-y -Wno-error=yacc". + +*** The display of warnings is now richer + + The option that controls a given warning is now displayed: + + foo.y:4.6: warning: type clash on default action: != [-Wother] + + In the case of warnings treated as errors, the prefix is changed from + "warning: " to "error: ", and the suffix is displayed, in a manner similar + to GCC, as [-Werror=CATEGORY]. + + For instance, where the previous version of Bison would report (and exit + with failure): + + bison: warnings being treated as errors + input.y:1.1: warning: stray ',' treated as white space + + it now reports: + + input.y:1.1: error: stray ',' treated as white space [-Werror=other] + +*** Deprecated constructs + + The new 'deprecated' warning category flags obsolete constructs whose + support will be discontinued. It is enabled by default. These warnings + used to be reported as 'other' warnings. + +*** Useless semantic types + + Bison now warns about useless (uninhabited) semantic types. Since + semantic types are not declared to Bison (they are defined in the opaque + %union structure), it is %printer/%destructor directives about useless + types that trigger the warning: + + %token term + %type nterm + %printer {} + %destructor {} + %% + nterm: term { $$ = $1; }; + + 3.28-34: warning: type is used, but is not associated to any symbol + 4.28-34: warning: type is used, but is not associated to any symbol + +*** Undefined but unused symbols + + Bison used to raise an error for undefined symbols that are not used in + the grammar. This is now only a warning. + + %printer {} symbol1 + %destructor {} symbol2 + %type symbol3 + %% + exp: "a"; + +*** Useless destructors or printers + + Bison now warns about useless destructors or printers. In the following + example, the printer for , and the destructor for are + useless: all symbols of (token1) already have a printer, and all + symbols of type (token2) already have a destructor. + + %token token1 + token2 + token3 + token4 + %printer {} token1 + %destructor {} token2 + +*** Conflicts + + The warnings and error messages about shift/reduce and reduce/reduce + conflicts have been normalized. For instance on the following foo.y file: + + %glr-parser + %% + exp: exp '+' exp | '0' | '0'; + + compare the previous version of bison: + + $ bison foo.y + foo.y: conflicts: 1 shift/reduce, 2 reduce/reduce + $ bison -Werror foo.y + bison: warnings being treated as errors + foo.y: conflicts: 1 shift/reduce, 2 reduce/reduce + + with the new behavior: + + $ bison foo.y + foo.y: warning: 1 shift/reduce conflict [-Wconflicts-sr] + foo.y: warning: 2 reduce/reduce conflicts [-Wconflicts-rr] + $ bison -Werror foo.y + foo.y: error: 1 shift/reduce conflict [-Werror=conflicts-sr] + foo.y: error: 2 reduce/reduce conflicts [-Werror=conflicts-rr] + + When %expect or %expect-rr is used, such as with bar.y: + + %expect 0 + %glr-parser + %% + exp: exp '+' exp | '0' | '0'; + + Former behavior: + + $ bison bar.y + bar.y: conflicts: 1 shift/reduce, 2 reduce/reduce + bar.y: expected 0 shift/reduce conflicts + bar.y: expected 0 reduce/reduce conflicts + + New one: + + $ bison bar.y + bar.y: error: shift/reduce conflicts: 1 found, 0 expected + bar.y: error: reduce/reduce conflicts: 2 found, 0 expected + +** Additional yylex/yyparse arguments + + The new directive %param declares additional arguments to both yylex and + yyparse. The %lex-param, %parse-param, and %param directives support one + or more arguments. Instead of + + %lex-param {arg1_type *arg1} + %lex-param {arg2_type *arg2} + %parse-param {arg1_type *arg1} + %parse-param {arg2_type *arg2} + + one may now declare + + %param {arg1_type *arg1} {arg2_type *arg2} + +** Java skeleton improvements + + The constants for token names were moved to the Lexer interface. Also, it + is possible to add code to the parser's constructors using "%code init" + and "%define init_throws". + +** C++ skeletons improvements + +*** The parser header is no longer mandatory (lalr1.cc, glr.cc) + + Using %defines is now optional. Without it, the needed support classes + are defined in the generated parser, instead of additional files (such as + location.hh, position.hh and stack.hh). + +*** Locations are no longer mandatory (lalr1.cc, glr.cc) + + Both lalr1.cc and glr.cc no longer require %location. + +*** syntax_error exception (lalr1.cc) + + The C++ parser features a syntax_error exception, which can be + thrown from the scanner or from user rules to raise syntax errors. + This facilitates reporting errors caught in sub-functions (e.g., + rejecting too large integral literals from a conversion function + used by the scanner, or rejecting invalid combinations from a + factory invoked by the user actions). + +** Variable api.token.prefix + + The variable api.token.prefix changes the way tokens are identified in + the generated files. This is especially useful to avoid collisions + with identifiers in the target language. For instance + + %token FILE for ERROR + %define api.token.prefix "TOK_" + %% + start: FILE for ERROR; + + will generate the definition of the symbols TOK_FILE, TOK_for, and + TOK_ERROR in the generated sources. In particular, the scanner must + use these prefixed token names, although the grammar itself still + uses the short names (as in the sample rule given above). + +** Renamed %define variables + + The following variables have been renamed for consistency. Backward + compatibility is ensured, but upgrading is recommended. + + lr.default-reductions -> lr.default-reduction + lr.keep-unreachable-states -> lr.keep-unreachable-state + namespace -> api.namespace + +** Variable parse.error + + This variable controls the verbosity of error messages. The use of the + %error-verbose directive is deprecated in favor of "%define parse.error + verbose". + +** Semantic predicates + + The new, experimental, semantic-predicate feature allows actions of the + form "%?{ BOOLEAN-EXPRESSION }", which cause syntax errors (as for + YYERROR) if the expression evaluates to 0, and are evaluated immediately + in GLR parsers, rather than being deferred. The result is that they allow + the programmer to prune possible parses based on the values of run-time + expressions. + +** The directive %expect-rr is now an error in non GLR mode + + It used to be an error only if used in non GLR mode, _and_ if there are + reduce/reduce conflicts. + +* Noteworthy changes in release ?.? (????-??-??) [?] + + ** %language is no longer an experimental feature. + + The introduction of this feature, in 2.4, was four years ago. The --language + option and the %language directive are no longer experimental. + ** New value for %define variable: api.pure full The %define variable api.pure requests a pure (reentrant) parser. However, diff --cc src/getargs.c index cf5af694,c480649d..77c1cbfb --- a/src/getargs.c +++ b/src/getargs.c @@@ -321,10 -307,8 +321,9 @@@ Operation modes:\n fputs (_("\ Parser:\n\ -L, --language=LANGUAGE specify the output programming language\n\ - (this is an experimental feature)\n\ -S, --skeleton=FILE specify the skeleton to use\n\ - -t, --debug instrument the parser for debugging\n\ + -t, --debug instrument the parser for tracing\n\ + same as `-Dparse.trace'\n\ --locations enable location support\n\ -D, --define=NAME[=VALUE] similar to '%define NAME \"VALUE\"'\n\ -F, --force-define=NAME[=VALUE] override '%define NAME \"VALUE\"'\n\ diff --cc src/scan-code.l index 1024913a,560d3435..c16515dd --- a/src/scan-code.l +++ b/src/scan-code.l @@@ -225,8 -224,12 +225,12 @@@ ref -?[0-9]+|{id}|"["{id}"]"|"$ if (outer_brace && !yacc_flag && language_prio == default_prio && skeleton_prio == default_prio && need_semicolon && ! in_cpp) { - complain (loc, Wdeprecated, _("a ';' might be needed at the end of action code")); - complain (loc, Wdeprecated, _("future versions of Bison will not add the ';'")); + unsigned int indent = 0; - warn_at_indent (*loc, &indent, - _("a ';' might be needed at the end of action code")); ++ complain_indent (loc, Wdeprecated, &indent, ++ _("a ';' might be needed at the end of action code")); + indent += SUB_INDENT; - warn_at_indent (*loc, &indent, - _("future versions of Bison will not add the ';'")); ++ complain_indent (loc, Wdeprecated | silent, &indent, ++ _("future versions of Bison will not add the ';'")); obstack_1grow (&obstack_for_string, ';'); } diff --cc tests/actions.at index c148391d,5e897a2e..6d160efd --- a/tests/actions.at +++ b/tests/actions.at @@@ -1606,42 -1585,42 +1606,42 @@@ string;" AT_BISON_OPTION_POPDEFS AT_BISON_CHECK([[-o input.c input.y]], [0], [], -[[input.y:8.48: warning: a ';' might be needed at the end of action code +[[input.y:8.48: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:8.48: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:8.48: future versions of Bison will not add the ';' -input.y:9.48: warning: a ';' might be needed at the end of action code +input.y:9.48: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:9.48: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:9.48: future versions of Bison will not add the ';' -input.y:10.48: warning: a ';' might be needed at the end of action code +input.y:10.48: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:10.48: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:10.48: future versions of Bison will not add the ';' -input.y:11.48: warning: a ';' might be needed at the end of action code +input.y:11.48: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:11.48: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:11.48: future versions of Bison will not add the ';' -input.y:12.48: warning: a ';' might be needed at the end of action code +input.y:12.48: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:12.48: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:12.48: future versions of Bison will not add the ';' -input.y:13.48: warning: a ';' might be needed at the end of action code +input.y:13.48: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:13.48: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:13.48: future versions of Bison will not add the ';' -input.y:20.1: warning: a ';' might be needed at the end of action code +input.y:20.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:20.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:20.1: future versions of Bison will not add the ';' -input.y:21.1: warning: a ';' might be needed at the end of action code +input.y:21.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:21.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:21.1: future versions of Bison will not add the ';' -input.y:22.1: warning: a ';' might be needed at the end of action code +input.y:22.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:22.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:22.1: future versions of Bison will not add the ';' -input.y:23.1: warning: a ';' might be needed at the end of action code +input.y:23.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:23.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:23.1: future versions of Bison will not add the ';' -input.y:24.1: warning: a ';' might be needed at the end of action code +input.y:24.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:24.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:24.1: future versions of Bison will not add the ';' -input.y:25.1: warning: a ';' might be needed at the end of action code +input.y:25.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:25.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:25.1: future versions of Bison will not add the ';' -input.y:31.1: warning: a ';' might be needed at the end of action code +input.y:31.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:31.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:31.1: future versions of Bison will not add the ';' -input.y:32.1: warning: a ';' might be needed at the end of action code +input.y:32.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:32.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:32.1: future versions of Bison will not add the ';' -input.y:33.1: warning: a ';' might be needed at the end of action code +input.y:33.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:33.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:33.1: future versions of Bison will not add the ';' -input.y:34.1: warning: a ';' might be needed at the end of action code +input.y:34.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:34.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:34.1: future versions of Bison will not add the ';' -input.y:35.1: warning: a ';' might be needed at the end of action code +input.y:35.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:35.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:35.1: future versions of Bison will not add the ';' -input.y:36.1: warning: a ';' might be needed at the end of action code +input.y:36.1: warning: a ';' might be needed at the end of action code [-Wdeprecated] - input.y:36.1: warning: future versions of Bison will not add the ';' [-Wdeprecated] + input.y:36.1: future versions of Bison will not add the ';' ]]) AT_MATCHES_CHECK([input.c], [[/\* TEST:N:2 \*/ \}$]], [[3]])