More.

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.
 
+This will be possible with a Bison parser for the grammar, as it will
+make it much easier to extend the grammar.
+
 * 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>
@@ -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.)
 
-
 * $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).
 
+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