mirror of
https://git.savannah.gnu.org/git/bison.git
synced 2026-03-15 07:13:02 +00:00
news: update
This commit is contained in:
14
NEWS
14
NEWS
@@ -2,6 +2,10 @@ GNU Bison NEWS
|
|||||||
|
|
||||||
* Noteworthy changes in release ?.? (????-??-??) [?]
|
* Noteworthy changes in release ?.? (????-??-??) [?]
|
||||||
|
|
||||||
|
** Bug fixes
|
||||||
|
|
||||||
|
Portability issues.
|
||||||
|
|
||||||
|
|
||||||
* Noteworthy changes in release 3.6.90 (2020-07-04) [beta]
|
* Noteworthy changes in release 3.6.90 (2020-07-04) [beta]
|
||||||
|
|
||||||
@@ -30,8 +34,11 @@ GNU Bison NEWS
|
|||||||
First derivation exp ::=[ exp ::=[ exp '+' exp • ] '/' exp ]
|
First derivation exp ::=[ exp ::=[ exp '+' exp • ] '/' exp ]
|
||||||
Second derivation exp ::=[ exp '+' exp ::=[ exp • '/' exp ] ]
|
Second derivation exp ::=[ exp '+' exp ::=[ exp • '/' exp ] ]
|
||||||
|
|
||||||
|
When Bison is installed with text styling enabled, the example is actually
|
||||||
|
shown twice, with colors highlighting the ambiguity.
|
||||||
|
|
||||||
This is a shift/reduce conflict caused by none of the operators having
|
This is a shift/reduce conflict caused by none of the operators having
|
||||||
precedence, so the example can be parsed in the two ways shown. When
|
precedence, so the example can be parsed in the two ways shown. When
|
||||||
bison cannot find an example that can be derived in two ways, it instead
|
bison cannot find an example that can be derived in two ways, it instead
|
||||||
generates two examples that are the same up until the dot:
|
generates two examples that are the same up until the dot:
|
||||||
|
|
||||||
@@ -43,6 +50,11 @@ GNU Bison NEWS
|
|||||||
In these cases, the parser usually doesn't have enough lookahead to
|
In these cases, the parser usually doesn't have enough lookahead to
|
||||||
differentiate the two given examples.
|
differentiate the two given examples.
|
||||||
|
|
||||||
|
The counterexamples are "focused": in two different ways. First, they do
|
||||||
|
not clutter the output with all the derivations from the start symbol,
|
||||||
|
rather they start on the "conflicted nonterminal". They go straight to the
|
||||||
|
point. Second, they don't "expand" nonterminal symbols uselessly.
|
||||||
|
|
||||||
*** File prefix mapping
|
*** File prefix mapping
|
||||||
|
|
||||||
Contributed by Joshua Watt.
|
Contributed by Joshua Watt.
|
||||||
|
|||||||
Reference in New Issue
Block a user