X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=8c3fdf98276d69cc7d3bd723fd84aaeae3357602;hp=2cec7771eceace09ce4de4ae750859038e9000c7;hb=ae0cef03f2e46f6ae6438f9a3e60ca36ff1a4643;hpb=3c03a0a1131b46a23ccfdeab2cb4fbd59ee05b7a

diff --git a/TODO b/TODO
index 2cec777..8c3fdf9 100644
--- a/TODO
+++ b/TODO
@@ -1,18 +1,27 @@
 _____________________________________________________________________________
 Immediately
 
-- Migrate Demo.java -> MetaGrammar.java
-    - Figure out serialization
+  - needs/hates/follow API ugliness
 
-- Clean up the prioritized-match garbage
- - evil problems with      (x y? z /ws)
+  - Topology crap is kinda messed up
+      - Atom should be a topology, shouldn't it?
 
+  - 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
 
-  - better ambiguity debugging tools / visualization
+  - 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
 
@@ -24,8 +33,6 @@ v1.1
       - RFC2822 (email message/headers)
   - clean up the whole Walk situation (?)
 
-  - what if Tree<> could unwrap itself?
-
 
 ______________________________________________________________________________
 Soon
@@ -37,10 +44,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)