X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/5d27808262de3a1759f1ee784be6b0cd2733bac5..e0ac9b4bb068c17dacfa6a6b2b4d8157d27bf8ee:/TODO diff --git a/TODO b/TODO index b6e1a20a..7d6f20ea 100644 --- a/TODO +++ b/TODO @@ -36,7 +36,7 @@ Catch up with yacc.c. ** GLR How would Paul like to display the conflicted actions? In particular, -what when two reductions are possible on a given look-ahead token, but one is +what when two reductions are possible on a given lookahead token, but one is part of $default. Should we make the two reductions explicit, or just keep $default? See the following point. @@ -56,6 +56,9 @@ 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 + for an approach. + * Extensions @@ -310,9 +313,8 @@ at the proper place to bison.simple. Ditto for YYACT_PROLOGUE. I was wondering what you think about adding YYACT_PROLOGUE/EPILOGUE to bison. If you're interested, I'll work on a patch. -* Move to Graphviz -Well, VCG seems really dead. Move to Graphviz instead. Also, equip -the parser with a means to create the (visual) parse tree. +* Better graphics +Equip the parser with a means to create the (visual) parse tree. -----