X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/959e5f515a22942a4910ada629ee98540d90d940..249d3236d0dd1d6051e0d30aa723fce01eb04db1:/TODO?ds=sidebyside diff --git a/TODO b/TODO index 1bc0e85e..3b2bf690 100644 --- a/TODO +++ b/TODO @@ -29,7 +29,7 @@ Currently, the GLR parser cannot compile with a C++ compiler. ** GLR How would Paul like to display the conflicted actions? In particular, -what when two reductions are possible on a given lookahead, but one is +what when two reductions are possible on a given look-ahead token, but one is part of $default. Should we make the two reductions explicit, or just keep $default? See the following point. @@ -81,7 +81,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 @@ -118,6 +117,20 @@ to avoid falling into another CPP mistake. ** -D, --define-muscle NAME=VALUE To define muscles via cli. Or maybe support directly NAME=VALUE? +** XML Output +There are couple of available extensions of Bison targeting some XML +output. Some day we should consider including them. One issue is +that they seem to be quite orthogonal to the parsing technique, and +seem to depend mostly on the possibility to have some code triggered +for each reduction. As a matter of fact, such hooks could also be +used to generate the yydebug traces. Some generic scheme probably +exists in there. + +XML output for GNU Bison and gcc + http://www.cs.may.ie/~jpower/Research/bisonXML/ + +XML output for GNU Bison + http://yaxx.sourceforge.net/ * Unit rules Maybe we could expand unit rules, i.e., transform @@ -161,7 +174,7 @@ There are a couple of proposed outputs: which is based on Bison. -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. @@ -179,7 +192,9 @@ Paul notes: PDP-10 ports :-) but they should probably be documented somewhere. - + More importantly, Bison does not currently allow NUL bytes in + tokens, either via escapes (e.g., "x\0y") or via a NUL byte in + the source code. This should get fixed. * --graph Show reductions. [] @@ -324,7 +339,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, 2004 Free Software Foundation, Inc. This file is part of GNU Bison.