X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/51cbef6f6332c3ec10bc64182bcf2f83351d7dff..3c40d0b52d288f1b03a6ebdebea3d6793870358c:/TODO

diff --git a/TODO b/TODO
index 573e0867..b6e1a20a 100644
--- a/TODO
+++ b/TODO
@@ -12,6 +12,15 @@ They should not: it is not documented.  But if they need to, let's
 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.
@@ -87,11 +96,6 @@ we should be able to have:
 
 Or something like this.
 
-** yysymprint interface
-It should be improved, in particular when using Bison features such as
-locations, and YYPARSE_PARAMS.  For the time being, it is almost
-recommended to yyprint to steal internal variables...
-
 ** %if and the like
 It should be possible to have %if/%else/%endif.  The implementation is
 not clear: should it be lexical or syntactic.  Vadim Maslow thinks it
@@ -182,28 +186,16 @@ Paul notes:
 	the source code.  This should get fixed.
 
 * --graph
-Show reductions.	[]
+Show reductions.
 
 * Broken options ?
-** %no-parser		[]
-** %token-table		[]
-** Skeleton strategy.	[]
-Must we keep %no-parser?
-	     %token-table?
+** %no-parser
+** %token-table
+** Skeleton strategy
+Must we keep %no-parser?  %token-table?
 
 * src/print_graph.c
-Find the best graph parameters.	[]
-
-* doc/bison.texinfo
-** Update
-informations about ERROR_VERBOSE.	[]
-** Add explanations about
-skeleton muscles.	[]
-%skeleton.		[]
-
-* testsuite
-** tests/pure-parser.at	[]
-New tests.
+Find the best graph parameters.
 
 * BTYacc
 See if we can integrate backtracking in Bison.  Charles-Henri de