Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-19 17:23:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update.

Browse Source
This commit is contained in:
Akim Demaille
2003-04-29 09:16:50 +00:00
parent 211074caca
commit ca752c3497
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
TODO
View File

@@ -81,7 +81,6 @@ we should be able to have:
Or something like this. Or something like this.
** yysymprint interface ** 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 almost 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 ** -D, --define-muscle NAME=VALUE
To define muscles via cli. Or maybe support directly 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 * Unit rules
Maybe we could expand unit rules, i.e., transform Maybe we could expand unit rules, i.e., transform