X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=d58eb06ef9389c940956de251ed50049cd4b89f1;hp=f059a77b4fd96ab9c8abf7dd9e4c29df20cad354;hb=280e93a7eec101178dc81f8009eedb2916271f09;hpb=0ab024f487647f99eb000345c29c2f8e9b52a200

diff --git a/TODO b/TODO
index f059a77..d58eb06 100644
--- a/TODO
+++ b/TODO
@@ -1,18 +1,22 @@
 _____________________________________________________________________________
 Immediately
 
-  - I still don't like Atom.Infer and Atom.Invert...
-
-  - better ambiguity debugging tools
+  - do Forest/Tree still need a Region?
+  - reconsider the degree of genericization
+  - GraphViz stuff pollutes the API...
+  - Forest needs a "manual access" API
+      - the unwrap bit in Forest makes it really hard to expose an API for forests
 
+  - evil problems with      (x y? z /ws)
   - ParseFailed, GSS, Walk, Parser, Sequence, Forest
-
-  - Fix the metagrammar (really?)
-      - evil problems with      (x y? z /ws)
-
   - copyright notices
   - documentation
 
+  - grammar highlighting?
+  - comment indentation vs block indentation?
+  - { and } in <pre>
+  - recursive { { foo } }
+
 ______________________________________________________________________________
 v1.1
 
@@ -24,8 +28,6 @@ v1.1
       - RFC2822 (email message/headers)
   - clean up the whole Walk situation (?)
 
-  - what if Tree<> could unwrap itself?
-
 
 ______________________________________________________________________________
 Soon
@@ -37,10 +39,6 @@ Soon
        - eliminated statically?
 
   - substring parsing for better error messages
-  - "lift" cases:
-      - right now I can only lift the last child in a forest...  begs
-        the question of what the right representation for Forests is
-        if we need to be able to do lift operations on it.
 
   - Parameterized LR
   - "Regular Right Part" grammars (NP Chapman, etc)