195 |
A round of memory leak clean ups would be most welcome. Dmalloc, |
A round of memory leak clean ups would be most welcome. Dmalloc, |
196 |
Checker GCC, Electric Fence, or Valgrind: you chose your tool. |
Checker GCC, Electric Fence, or Valgrind: you chose your tool. |
197 |
|
|
|
* Memory leaks in the parser |
|
|
The same applies to the generated parsers. In particular, this is |
|
|
critical for user data: when aborting a parsing, when handling the |
|
|
error token etc., we often throw away yylval without giving a chance |
|
|
of cleaning it up to the user. |
|
|
|
|
198 |
* --graph |
* --graph |
199 |
Show reductions. [] |
Show reductions. [] |
200 |
|
|
302 |
This will be possible with a Bison parser for the grammar, as it will |
This will be possible with a Bison parser for the grammar, as it will |
303 |
make it much easier to extend the grammar. |
make it much easier to extend the grammar. |
304 |
|
|
|
* Parsing grammars |
|
|
Rewrite the reader in Flex/Bison. There will be delicate parts, in |
|
|
particular, expect the scanner to be hard to write. Many interesting |
|
|
features cannot be implemented without such a new reader. |
|
|
|
|
|
I'm on it! I already have a proto that parses (but the actions are |
|
|
not fully written yet). -- Akim |
|
|
|
|
305 |
* $undefined |
* $undefined |
306 |
From Hans: |
From Hans: |
307 |
- If the Bison generated parser experiences an undefined number in the |
- If the Bison generated parser experiences an undefined number in the |