X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=b476721810e06c77dbed7bb0ea8aef0be7ee0f96;hp=fb89b5213e015b7fc5f814f9f3f413a2d26e8634;hb=b8a597c8d1a29afc24f9b89f726d5b1a9b9aeec1;hpb=e5d6a50df43fa50f217b30b0959a1d39f65b621c

diff --git a/TODO b/TODO
index fb89b52..b476721 100644
--- a/TODO
+++ b/TODO
@@ -1,11 +1,27 @@
 _____________________________________________________________________________
 Immediately
 
-  - clean up the whole Walk situation (?)
+  - Sequence shouldn't be an Element -> make Union.add(Element)
+  - Should Tree<T> really be type-parameterized?
+
+  - More topology untangling
+  - needs/hates/follow API ugliness
 
-  - decent/better error messages
-      - fix the location stuff, it's broken
+  - 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
+  - copyright notices
+  - documentation
+
+  - grammar highlighting?
+  - comment indentation vs block indentation?
+  - { and } in <pre>
+  - recursive { { foo } }
 
 ______________________________________________________________________________
 v1.1
@@ -16,6 +32,7 @@ v1.1
       - TeX (math?)
       - URL (RFC)
       - RFC2822 (email message/headers)
+  - clean up the whole Walk situation (?)
 
 
 ______________________________________________________________________________
@@ -28,10 +45,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)
@@ -40,6 +53,9 @@ Soon
   - inference of rejections for literals
   - "prefer whitespace higher up" (?)
 
+  - Labeled edges on trees (associate a label with each slot in the
+    child array in Forest.Body?  might make equality tough) --
+    equivalent to Feature Structures.  Colon-labeling.
 
 ______________________________________________________________________________
 Later