81 |
|
|
82 |
Or something like this. |
Or something like this. |
83 |
|
|
|
|
|
84 |
** yysymprint interface |
** yysymprint interface |
85 |
It should be improved, in particular when using Bison features such as |
It should be improved, in particular when using Bison features such as |
86 |
locations, and YYPARSE_PARAMS. For the time being, it is almost |
locations, and YYPARSE_PARAMS. For the time being, it is almost |
117 |
** -D, --define-muscle NAME=VALUE |
** -D, --define-muscle NAME=VALUE |
118 |
To define muscles via cli. Or maybe support directly NAME=VALUE? |
To define muscles via cli. Or maybe support directly NAME=VALUE? |
119 |
|
|
120 |
|
** XML Output |
121 |
|
There are couple of available extensions of Bison targeting some XML |
122 |
|
output. Some day we should consider including them. One issue is |
123 |
|
that they seem to be quite orthogonal to the parsing technique, and |
124 |
|
seem to depend mostly on the possibility to have some code triggered |
125 |
|
for each reduction. As a matter of fact, such hooks could also be |
126 |
|
used to generate the yydebug traces. Some generic scheme probably |
127 |
|
exists in there. |
128 |
|
|
129 |
|
XML output for GNU Bison and gcc |
130 |
|
http://www.cs.may.ie/~jpower/Research/bisonXML/ |
131 |
|
|
132 |
|
XML output for GNU Bison |
133 |
|
http://yaxx.sourceforge.net/ |
134 |
|
|
135 |
* Unit rules |
* Unit rules |
136 |
Maybe we could expand unit rules, i.e., transform |
Maybe we could expand unit rules, i.e., transform |