Do not use @output_header_name@ unless

[bison.git] / TODO

diff --git a/TODO b/TODO
index 436fa0d38c48049db13d4e5154c56ff821ff7db9..1bc0e85e1b0f43c683eba6d458b239e5b06f3b4e 100644 (file)
--- a/TODO
+++ b/TODO
@@ -17,16 +17,8 @@ Write a first documentation for C++ output.
 
 
 * Documentation
 
 
 * Documentation

-Before releasing, make sure the documentation refers to the current
-`output' format.
-
-
-* Error messages
-Some are really funky.  For instance
-
-       type clash (`%s' `%s') on default action
-
-is really weird.  Revisit them all.
+Before releasing, make sure the documentation ("Understanding your
+parser") refers to the current `output' format.

 
 
 * GLR & C++
 
 
 * GLR & C++


@@ -60,10 +52,40 @@ DeRemer and Penello: they already provide the algorithm.
 
 * Extensions
 
 
 * Extensions
 

-** yyerror, yysymprint interface
+** %destructor
+I think we should document it as experimental, and allow its use in
+the next releases.  But we also need to port it to GLR.  What about
+lalr1.cc?  Well, read what Hans reported, maybe we don't want
+%detructor.  On the other hand, there is no reason not to provide it:
+users can avoid its use.
+
+** $foo
+Have a look at the Lemon parser generator: instead of $1, $2 etc. they
+can name the values.  This is much more pleasant.  For instance:
+
+       exp (res): exp (a) '+' exp (b) { $res = $a + $b; };
+
+I love this.  I have been bitten too often by the removal of the
+symbol, and forgetting to shift all the $n to $n-1.  If you are
+unlucky, it compiles...
+
+** $-1
+We should find a means to provide an access to values deep in the
+stack.  For instance, instead of
+
+       baz: qux { $$ = $<foo>-1 + $<bar>0 + $1; }
+
+we should be able to have:
+
+  foo($foo) bar($bar) baz($bar): qux($qux) { $baz = $foo + $bar + $qux; }
+
+Or something like this.
+
+
+** yysymprint interface

 It should be improved, in particular when using Bison features such as
 It should be improved, in particular when using Bison features such as

-locations, and YYPARSE_PARAMS.  For the time being, it is recommended
-to #define yyerror and yyprint to steal internal variables...
+locations, and YYPARSE_PARAMS.  For the time being, it is almost
+recommended to yyprint to steal internal variables...

 
 ** Several %unions
 I think this is a pleasant (but useless currently) feature, but in the
 
 ** Several %unions
 I think this is a pleasant (but useless currently) feature, but in the


@@ -163,21 +185,11 @@ Paul notes:
 Show reductions.       []
 
 * Broken options ?
 Show reductions.       []
 
 * Broken options ?

-** %no-lines           [ok]

 ** %no-parser          []
 ** %no-parser          []

-** %pure-parser                []

 ** %token-table                []
 ** %token-table                []

-** Options which could use parse_dquoted_param ().
-Maybe transferred in lex.c.
-*** %skeleton          [ok]
-*** %output            []
-*** %file-prefix       []
-*** %name-prefix       []
-

 ** Skeleton strategy.  []
 Must we keep %no-parser?
             %token-table?
 ** Skeleton strategy.  []
 Must we keep %no-parser?
             %token-table?

-*** New skeletons.     []

 
 * src/print_graph.c
 Find the best graph parameters.        []
 
 * src/print_graph.c
 Find the best graph parameters.        []


@@ -193,10 +205,6 @@ skeleton muscles.  []
 ** tests/pure-parser.at        []
 New tests.
 
 ** tests/pure-parser.at        []
 New tests.
 

-* input synclines
-Some users create their foo.y files, and equip them with #line.  Bison
-should recognize these, and preserve them.
-

 * BTYacc
 See if we can integrate backtracking in Bison.  Charles-Henri de
 Boysson <de-boy_c@epita.fr> is working on this, and already has some
 * BTYacc
 See if we can integrate backtracking in Bison.  Charles-Henri de
 Boysson <de-boy_c@epita.fr> is working on this, and already has some