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

maint: update todo

Browse Source 
* TODO: Remove fixed items.
This commit is contained in:
Akim Demaille
2013-01-28 17:08:45 +01:00
parent 8458a41144
commit 15c14fdfb9
1 changed files with 0 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
TODO
View File

@@ -48,9 +48,6 @@ Get rid of it. The original idea is nice, but actually it makes
the code harder to follow, and uselessly different from the other the code harder to follow, and uselessly different from the other
skeletons. skeletons.
** Variable names.
What should we name `variant' and `lex_symbol'?
** Get rid of fake #lines [Bison: ...] ** Get rid of fake #lines [Bison: ...]
Possibly as simple as checking whether the column number is nonnegative. Possibly as simple as checking whether the column number is nonnegative.
@@ -77,9 +74,6 @@ since it is no longer bound to a particular parser, it's just a
** Rename LR0.cc ** Rename LR0.cc
as lr0.cc, why upper case? as lr0.cc, why upper case?
** bench several bisons.
Enhance bench.pl with %b to run different bisons.
* Various * Various
** YYERRCODE ** YYERRCODE
Defined to 256, but not used, not documented. Probably the token Defined to 256, but not used, not documented. Probably the token
@@ -143,12 +137,6 @@ really possible? The test suite does not exercise this case.
This shows that it would be interesting to manage to install skeleton This shows that it would be interesting to manage to install skeleton
coverage analysis to the test suite. coverage analysis to the test suite.
** Table definitions
It should be very easy to factor the definition of the various tables,
including the separation bw declaration and definition. See for
instance b4_table_define in lalr1.cc. This way, we could even factor
C vs. C++ definitions.
* From lalr1.cc to yacc.c * From lalr1.cc to yacc.c
** Single stack ** Single stack
Merging the three stacks in lalr1.cc simplified the code, prompted for Merging the three stacks in lalr1.cc simplified the code, prompted for
@@ -274,9 +262,6 @@ Paul notes:
tokens, either via escapes (e.g., "x\0y") or via a NUL byte in tokens, either via escapes (e.g., "x\0y") or via a NUL byte in
the source code. This should get fixed. the source code. This should get fixed.
* --graph
Show reductions.
* Broken options ? * Broken options ?
** %token-table ** %token-table
** Skeleton strategy ** Skeleton strategy