TODO: Mention that we should allow NUL bytes in tokens.

[bison.git] / TODO

diff --git a/TODO b/TODO
index a300524021ff90a3e73eb74cfc5ec8e6220e474d..3b2bf6905efb7da2e566cdd874ea01b73c551a1f 100644 (file)
--- a/TODO
+++ b/TODO
@@ -29,7 +29,7 @@ Currently, the GLR parser cannot compile with a C++ compiler.
 
 **  GLR
 How would Paul like to display the conflicted actions?  In particular,
-what when two reductions are possible on a given lookahead, but one is
+what when two reductions are possible on a given look-ahead token, but one is
 part of $default.  Should we make the two reductions explicit, or just
 keep $default?  See the following point.
 
@@ -192,7 +192,9 @@ Paul notes:
        PDP-10 ports :-) but they should probably be documented
        somewhere.
 
-
+       More importantly, Bison does not currently allow NUL bytes in
+       tokens, either via escapes (e.g., "x\0y") or via a NUL byte in
+       the source code.  This should get fixed.
 
 * --graph
 Show reductions.       []
@@ -337,7 +339,7 @@ the parser with a means to create the (visual) parse tree.
 
 -----
 
-Copyright (C) 2001, 2002, 2003 Free Software Foundation, Inc.
+Copyright (C) 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
 
 This file is part of GNU Bison.