X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/455671735e6f4e9712c2f5ac1bc153b07b33e67b..75ad86eebd3f49dff81976eb83036eb7b7793e68:/TODO diff --git a/TODO b/TODO index 76ca7362..94bd12c8 100644 --- a/TODO +++ b/TODO @@ -12,6 +12,8 @@ They should not: it is not documented. But if they need to, let's find something clean (not like YYLSP_NEEDED...). +* Installation + * Documentation Before releasing, make sure the documentation ("Understanding your parser") refers to the current `output' format. @@ -27,7 +29,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. @@ -47,6 +49,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 @@ -142,23 +147,6 @@ Are there any Texinfo standards for bibliography? * Java, Fortran, etc. -** Java - -There are a couple of proposed outputs: - -- BYACC/J - which is based on Byacc. - - -- Bison Java - which is based on Bison. - - -Sebastien Serrurier (serrur_s@epita.fr) is working on this: he is -expected to contact the authors, design the output, and implement it -into Bison. - - * Coding system independence Paul notes: @@ -219,9 +207,6 @@ It is unfortunate that there is a total order for precedence. It makes it impossible to have modular precedence information. We should move to partial orders (sounds like series/parallel orders to me). -This will be possible with a Bison parser for the grammar, as it will -make it much easier to extend the grammar. - ** Correlation b/w precedence and associativity Also, I fail to understand why we have to assign the same associativity to operators with the same precedence. For instance, @@ -301,9 +286,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. -----