X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/1fa19a769721658bb53177596531afbbea8b4e1c..bb4b189b9c94f66acfe0239b22f295d1314e173e:/NEWS diff --git a/NEWS b/NEWS index 60a62e1d..e06cb77a 100644 --- a/NEWS +++ b/NEWS @@ -62,6 +62,8 @@ GNU Bison NEWS Changes in Bison 2.7 introduced a dependency on FILE and fprintf when locations are enabled. This is fixed. +*** Warnings about useless %pure-parser/%define api.pure are restored + ** Diagnostics reported by Bison Most of these features were contributed by Théophile Ranquet and Victor @@ -256,6 +258,23 @@ GNU Bison NEWS %param {arg1_type *arg1} {arg2_type *arg2} +** Types of values for %define variables + + Bison used to make no difference between '%define foo bar' and '%define + foo "bar"'. The former is now called a 'keyword value', and the latter a + 'string value'. A third kind was added: 'code values', such as '%define + foo {bar}'. + + Keyword variables are used for fixed value sets, e.g., + + %define lr.type lalr + + Code variables are used for value in the target language, e.g., + + %define api.value.type {struct semantic_type} + + String variables are used remaining cases, e.g. file names. + ** Variable api.token.prefix The variable api.token.prefix changes the way tokens are identified in @@ -263,7 +282,7 @@ GNU Bison NEWS with identifiers in the target language. For instance %token FILE for ERROR - %define api.token.prefix "TOK_" + %define api.token.prefix {TOK_} %% start: FILE for ERROR; @@ -294,12 +313,13 @@ GNU Bison NEWS yylval.ival = 42; return INT; yylval.sval = "42"; return STRING; - The %define variable api.value.type supports several special values. The - value "union" means that the user provides genuine types, not union member - names such as "ival" and "sval" above (WARNING: will fail if + The %define variable api.value.type supports both keyword and code values. + + The keyword value 'union' means that the user provides genuine types, not + union member names such as "ival" and "sval" above (WARNING: will fail if -y/--yacc/%yacc is enabled). - %define api.value.type "union" + %define api.value.type union %token INT "integer" %token STRING "string" %printer { fprintf (yyo, "%d", $$); } @@ -309,15 +329,15 @@ GNU Bison NEWS yylval.INT = 42; return INT; yylval.STRING = "42"; return STRING; - The value "variant" is somewhat equivalent, but for C++ special provision - is made to allow classes to be used (more about this below). + The keyword value variant is somewhat equivalent, but for C++ special + provision is made to allow classes to be used (more about this below). - %define api.value.type "variant" + %define api.value.type variant %token INT "integer" %token STRING "string" - Any other name is a user type to use. This is where YYSTYPE used to be - used. + Code values (in braces) denote user defined types. This is where YYSTYPE + used to be used. %code requires { @@ -334,7 +354,7 @@ GNU Bison NEWS } u; }; } - %define api.value.type "struct my_value" + %define api.value.type {struct my_value} %token INT "integer" %token STRING "string" %printer { fprintf (yyo, "%d", $$); } @@ -569,6 +589,21 @@ GNU Bison NEWS ... } +*** C++ locations + + There are operator- and operator-= for 'location'. Negative line/column + increments can no longer underflow the resulting value. + +* Noteworthy changes in release ?.? (????-??-??) [?] + +** Bug fixes + +*** Fix compiler attribute portability (yacc.c) + + With locations enabled, __attribute__ was used unprotected. + +*** Fix some compiler warnings (lalr1.cc) + * Noteworthy changes in release 2.7 (2012-12-12) [stable] ** Bug fixes