Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-18 16:53:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

news, todo: update

Browse Source
This commit is contained in:
Akim Demaille
2020-06-29 06:54:01 +02:00
parent 5234c8390f
commit 84ef175287
2 changed files with 4 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
NEWS
View File

@@ -6,6 +6,8 @@ GNU Bison NEWS
*** Counterexample Generation *** Counterexample Generation
Contributed by Vincent Imbimbo.
When given `--report=counterexamples` or `-Wcounterexamples`, bison will When given `--report=counterexamples` or `-Wcounterexamples`, bison will
now output counterexamples for conflicts in the grammar. These are now output counterexamples for conflicts in the grammar. These are
strings in the grammar which can be parsed in two ways due to the strings in the grammar which can be parsed in two ways due to the
@@ -30,6 +32,8 @@ GNU Bison NEWS
*** File prefix mapping *** File prefix mapping
Contributed by Joshua Watt.
Bison learned a new argument, `--file-prefix-map OLD=NEW`. Any file path Bison learned a new argument, `--file-prefix-map OLD=NEW`. Any file path
in the output (specifically `#line` directives and `#ifdef` header guards) in the output (specifically `#line` directives and `#ifdef` header guards)
that begins with the prefix OLD will have it replaced with the prefix NEW, that begins with the prefix OLD will have it replaced with the prefix NEW,

17
TODO
View File

@@ -432,16 +432,6 @@ undocumented ''features''. Maybe an empty action ought to be
presented too. Shall we try to make a single grammar with all these presented too. Shall we try to make a single grammar with all these
features, or should we have several very small grammars? features, or should we have several very small grammars?
** --report=conflict-path
Provide better assistance for understanding the conflicts by providing
a sample text exhibiting the (LALR) ambiguity. See the paper from
DeRemer and Penello: they already provide the algorithm.
** Statically check for potential ambiguities in GLR grammars
See <http://www.lsv.fr/~schmitz/pub/expamb.pdf> for an approach.
An Experimental Ambiguity Detection Tool ∗ Sylvain Schmitz
LORIA, INRIA Nancy - Grand Est, Nancy, France
* Extensions * Extensions
** More languages? ** More languages?
Well, only if there is really some demand for it. Well, only if there is really some demand for it.
@@ -532,13 +522,6 @@ XML output for GNU Bison and gcc
XML output for GNU Bison XML output for GNU Bison
http://yaxx.sourceforge.net/ http://yaxx.sourceforge.net/
** Counterexample generation
https://lists.gnu.org/archive/html/bug-bison/2016-06/msg00000.html
http://www.cs.cornell.edu/andru/papers/cupex/
Andrew Myers and Vincent Imbimbo are working on this item, see
https://github.com/akimd/bison/issues/12
* Coding system independence * Coding system independence
Paul notes: Paul notes: