More.

diff --git a/TODO b/TODO
index 779cf9e56969c1d8f12a71d8ccac03721de4c331..ea033d1017b2cfd36d70a7fd87b9fdce581cf99f 100644 (file)
--- a/TODO
+++ b/TODO
@@ -269,8 +269,12 @@ It is unfortunate that there is a total order for precedence.  It
 makes it impossible to have modular precedence information.  We should
 move to partial orders.
 
 makes it impossible to have modular precedence information.  We should
 move to partial orders.
 

+This will be possible with a Bison parser for the grammar, as it will
+make it much easier to extend the grammar.
+

 * Parsing grammars
 * Parsing grammars

-Rewrite the reader in Bison.
+Rewrite the reader in Flex/Bison.  There will be delicate parts, in
+particular, expect the scanner to be hard to write.

 
 * Problems with aliases
 From: "Baum, Nathan I" <s0009525@chelt.ac.uk>
 
 * Problems with aliases
 From: "Baum, Nathan I" <s0009525@chelt.ac.uk>


@@ -318,7 +322,6 @@ everything, but the -v mode only tells you what you need for examining
 conflicts? (Or, perhaps, a "*** This state has N conflicts ***" marker above
 each state with conflicts.)
 
 conflicts? (Or, perhaps, a "*** This state has N conflicts ***" marker above
 each state with conflicts.)
 

-

 * $undefined
 From Hans:
 - If the Bison generated parser experiences an undefined number in the
 * $undefined
 From Hans:
 - If the Bison generated parser experiences an undefined number in the


@@ -341,6 +344,11 @@ $<type_name>$ = $<type_name>1. I therefore think that one should implement
 a Bison option where every typed default rule is explicitly written out
 (same typed ruled can of course be grouped together).
 
 a Bison option where every typed default rule is explicitly written out
 (same typed ruled can of course be grouped together).
 

+Note: Robert Anisko handles this.  He knows how to do it.
+
+* Documenting C++ output
+Write a first documentation for C++ output.
+

 * Warnings
 It would be nice to have warning support.  See how Autoconf handles
 them, it is fairly well described there.  It would be very nice to
 * Warnings
 It would be nice to have warning support.  See how Autoconf handles
 them, it is fairly well described there.  It would be very nice to