* src/getargs.c (flags_argmatch): Don't cause segmentation fault for

[bison.git] / TODO

diff --git a/TODO b/TODO
index 573e0867e69a4014bf598b5adc20979f30e23e65..ca610cc04dc8d79c710128cb4ba0130f57dfd52d 100644 (file)
--- 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...).
 
 
 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.
 * Documentation
 Before releasing, make sure the documentation ("Understanding your
 parser") refers to the current `output' format.


@@ -27,7 +36,7 @@ Catch up with yacc.c.
 
 **  GLR
 How would Paul like to display the conflicted actions?  In particular,
 
 **  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.
 
 part of $default.  Should we make the two reductions explicit, or just
 keep $default?  See the following point.
 


@@ -87,11 +96,6 @@ we should be able to have:
 
 Or something like this.
 
 
 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
 ** %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
        the source code.  This should get fixed.
 
 * --graph

-Show reductions.       []
+Show reductions.

 
 * Broken options ?
 
 * 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
 
 * 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
 
 * BTYacc
 See if we can integrate backtracking in Bison.  Charles-Henri de


@@ -318,9 +310,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.
 
 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.

 
 -----
 
 
 -----