X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/35fe08345edf43644a80a5987a50937c67e7c937..b09f4f48512c274a7574b6a22e4a1eac6a86fd61:/TODO?ds=sidebyside diff --git a/TODO b/TODO index ca610cc0..94bd12c8 100644 --- a/TODO +++ b/TODO @@ -14,13 +14,6 @@ find something clean (not like YYLSP_NEEDED...). * Installation -** Disable installation of yacc. - -Add an option to 'configure' that allows people to install Bison -without installing the yacc wrapper script or the rarely-used little -yacc library required by Posix. This is for people who prefer some -other implementation of yacc. - * Documentation Before releasing, make sure the documentation ("Understanding your parser") refers to the current `output' format. @@ -56,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 @@ -151,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: @@ -228,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,