bison-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

news: update


From: Akim Demaille
Subject: news: update
Date: Thu, 9 Jul 2020 21:31:34 +0200

commit 91e5a23ff2fea42de5939df22d99ea6e8cdbbb8f
Author: Akim Demaille <akim.demaille@gmail.com>
Date:   Sat Jul 4 17:02:15 2020 +0200

    news: update

diff --git a/NEWS b/NEWS
index 2882c72a..5b46b196 100644
--- a/NEWS
+++ b/NEWS
@@ -2,6 +2,10 @@ GNU Bison NEWS
 
 * Noteworthy changes in release ?.? (????-??-??) [?]
 
+** Bug fixes
+
+  Portability issues.
+
 
 * 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 ]
     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
-  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
   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
   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
 
   Contributed by Joshua Watt.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]