12 |
find something clean (not like YYLSP_NEEDED...). |
find something clean (not like YYLSP_NEEDED...). |
13 |
|
|
14 |
|
|
|
* readpipe |
|
|
|
|
|
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... |
|
|
|
|
|
|
|
15 |
* URGENT: Documenting C++ output |
* URGENT: Documenting C++ output |
16 |
Write a first documentation for C++ output. |
Write a first documentation for C++ output. |
17 |
|
|
29 |
is really weird. Revisit them all. |
is really weird. Revisit them all. |
30 |
|
|
31 |
|
|
|
* 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? |
|
|
|
|
|
|
|
32 |
* GLR & C++ |
* GLR & C++ |
33 |
Currently, the GLR parser cannot compile with a C++ compiler. |
Currently, the GLR parser cannot compile with a C++ compiler. |
34 |
|
|
86 |
char *sval; |
char *sval; |
87 |
} |
} |
88 |
|
|
89 |
|
** %if and the like |
90 |
|
It should be possible to have %if/%else/%endif. The implementation is |
91 |
|
not clear: should it be lexical or syntactic. Vadim Maslow thinks it |
92 |
|
must be in the scanner: we must not parse what is in a switched off |
93 |
|
part of %if. Akim Demaille thinks it should be in the parser, so as |
94 |
|
to avoid falling into another CPP mistake. |
95 |
|
|
96 |
|
** -D, --define-muscle NAME=VALUE |
97 |
|
To define muscles via cli. Or maybe support directly NAME=VALUE? |
98 |
|
|
99 |
|
|
100 |
* Unit rules |
* Unit rules |
101 |
Maybe we could expand unit rules, i.e., transform |
Maybe we could expand unit rules, i.e., transform |
102 |
|
|
198 |
should recognize these, and preserve them. |
should recognize these, and preserve them. |
199 |
|
|
200 |
* BTYacc |
* BTYacc |
201 |
See if we can integrate backtracking in Bison. Contact the BTYacc |
See if we can integrate backtracking in Bison. Charles-Henri de |
202 |
maintainers. |
Boysson <de-boy_c@epita.fr> is working on this, and already has some |
203 |
|
results. Vadim Maslow, the maintainer of BTYacc was contacted, and we |
204 |
|
stay in touch with him. Adjusting the Bison grammar parser will be |
205 |
|
needed to support some extra BTYacc features. This is less urgent. |
206 |
|
|
207 |
** Keeping the conflicted actions |
** Keeping the conflicted actions |
208 |
First, analyze the differences between byacc and btyacc (I'm referring |
First, analyze the differences between byacc and btyacc (I'm referring |