X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/217598dadc1d5aa72f430b1ac5584de8f385b596..0435d061f256fbd8cca6d1c53734ad652089e639:/TODO diff --git a/TODO b/TODO index 49775d18..1bc0e85e 100644 --- a/TODO +++ b/TODO @@ -1,31 +1,28 @@ -*- outline -*- -* URGENT: Documenting C++ output -Write a first documentation for C++ output. +* Header guards +From Franc,ois: should we keep the directory part in the CPP guard? -* Documentation -Before releasing, make sure the documentation refers to the current -`output' format. +* Yacc.c: CPP Macros -* Error messages -Some are really funky. For instance +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...). - type clash (`%s' `%s') on default action -is really weird. Revisit them all. +* URGENT: Documenting C++ output +Write a first documentation for C++ output. -* 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. +* Documentation +Before releasing, make sure the documentation ("Understanding your +parser") refers to the current `output' format. -* 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 $n on her -union, doesn't she? +* GLR & C++ +Currently, the GLR parser cannot compile with a C++ compiler. * Report @@ -53,12 +50,42 @@ a sample text exhibiting the (LALR) ambiguity. See the paper from DeRemer and Penello: they already provide the algorithm. -* Extentions +* Extensions + +** %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 { $$ = $-1 + $0 + $1; } + +we should be able to have: + + foo($foo) bar($bar) baz($bar): qux($qux) { $baz = $foo + $bar + $qux; } -** yyerror, yysymprint interface +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 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 @@ -81,6 +108,17 @@ When implementing multiple-%union support, bare the following in mind: 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 @@ -108,6 +146,25 @@ 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. + + +Sébastien 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: @@ -128,21 +185,11 @@ Paul notes: Show reductions. [] * Broken options ? -** %no-lines [ok] ** %no-parser [] -** %pure-parser [] ** %token-table [] -** Options which could use parse_dquoted_param (). -Maybe transfered in lex.c. -*** %skeleton [ok] -*** %output [] -*** %file-prefix [] -*** %name-prefix [] - ** Skeleton strategy. [] Must we keep %no-parser? %token-table? -*** New skeletons. [] * src/print_graph.c Find the best graph parameters. [] @@ -150,7 +197,7 @@ Find the best graph parameters. [] * doc/bison.texinfo ** Update informations about ERROR_VERBOSE. [] -** Add explainations about +** Add explanations about skeleton muscles. [] %skeleton. [] @@ -158,20 +205,19 @@ skeleton muscles. [] ** 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. Contact the BTYacc -maintainers. +See if we can integrate backtracking in Bison. Charles-Henri de +Boysson 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 to the executables). Find where the conflicts are preserved. ** Compare with the GLR tables -See how isomorphic the way BTYacc and the way the GLR adjustements in +See how isomorphic the way BTYacc and the way the GLR adjustments in Bison are compatible. *As much as possible* one should try to use the same implementation in the Bison executables. I insist: it should be very feasible to use the very same conflict tables.