Sync with latest FSF version.

[bison.git] / TODO

diff --git a/TODO b/TODO
index d57fef6128f6cdd34be80f1ea896bbbedc4f76d0..168b4e03c6302c9352fd6fd02961ef9a1fdfb710 100644 (file)
--- a/TODO
+++ b/TODO
@@ -5,16 +5,11 @@
 From Franc,ois: should we keep the directory part in the CPP guard?
 
 
 From Franc,ois: should we keep the directory part in the CPP guard?
 
 

-* readpipe
+* Yacc.c: CPP Macros

 
 

-It should be replaced to avoid tmp files and to improve portability.
-Also, as it is it does not call error () when execve fails, and
-therefore, running M4='m4 --version' bison will silently fail instead
-of:
-
-       bison: cannot run m4 --version: No such file or directory
-
-BTW: I would really like to be able to pass arguments to m4...
+Do some people use YYPURE, YYLSP_NEEDED like we do in the test suite?
+They should not: it is not documented.  But if they need to, let's
+find something clean (not like YYLSP_NEEDED...).

 
 
 * URGENT: Documenting C++ output
 
 
 * URGENT: Documenting C++ output


@@ -22,27 +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.
-
-
-* read_pipe.c
-This is not portable to DOS for instance.  Implement a more portable
-scheme.  Sources of inspiration include GNU diff, and Free Recode.
-
-
-* value_components_used
-Was defined but not used: where was it coming from?  It can't be to
-check if %union is used, since the user is free to $<foo>n on her
-union, doesn't she?
+Before releasing, make sure the documentation ("Understanding your
+parser") refers to the current `output' format.

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


@@ -76,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


@@ -102,6 +108,17 @@ When implementing multiple-%union support, bare the following in mind:
          char *sval;
        }
 
          char *sval;
        }
 

+** %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
+must be in the scanner: we must not parse what is in a switched off
+part of %if.  Akim Demaille thinks it should be in the parser, so as
+to avoid falling into another CPP mistake.
+
+** -D, --define-muscle NAME=VALUE
+To define muscles via cli.  Or maybe support directly NAME=VALUE?
+
+

 * Unit rules
 Maybe we could expand unit rules, i.e., transform
 
 * Unit rules
 Maybe we could expand unit rules, i.e., transform
 


@@ -144,7 +161,7 @@ There are a couple of proposed outputs:
   which is based on Bison.
   <http://www.goice.co.jp/member/mo/hack-progs/bison-java.html>
 
   which is based on Bison.
   <http://www.goice.co.jp/member/mo/hack-progs/bison-java.html>
 

-Sébastien Serrurier (serrur_s@epita.fr) is working on this: he is
+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.
 
 expected to contact the authors, design the output, and implement it
 into Bison.
 


@@ -168,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.        []


@@ -198,13 +205,12 @@ 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
 * BTYacc

-See if we can integrate backtracking in Bison.  Contact the BTYacc
-maintainers.
+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
+results.  Vadim Maslow, the maintainer of BTYacc was contacted, and we
+stay in touch with him.  Adjusting the Bison grammar parser will be
+needed to support some extra BTYacc features.  This is less urgent.

 
 ** Keeping the conflicted actions
 First, analyze the differences between byacc and btyacc (I'm referring
 
 ** Keeping the conflicted actions
 First, analyze the differences between byacc and btyacc (I'm referring


@@ -318,7 +324,7 @@ the parser with a means to create the (visual) parse tree.
 
 -----
 
 
 -----
 

-Copyright (C) 2001, 2002 Free Software Foundation, Inc.
+Copyright (C) 2001, 2002, 2003 Free Software Foundation, Inc.

 
 This file is part of GNU Bison.
 
 
 This file is part of GNU Bison.