X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=cecd2d440811bf4c47f6bb548edf6fc6d49f9678;hp=d7afed210b1b4c08633226d90b5e1fededf516d4;hb=111166986ad83b54d0cae5c03c2304d23e332f29;hpb=45d799349e635f1a99e3974e4504a43d5a7aaf33

diff --git a/TODO b/TODO
index d7afed2..cecd2d4 100644
--- a/TODO
+++ b/TODO
@@ -1,36 +1,29 @@
 _____________________________________________________________________________
 Immediately
 
-- If a top-level rule has labels but no head-tag, like this
-    Foo = a:Bar b:Baz
-  then infer the name of the rule it belongs to
+  - Sequence extends Element (?) -> then add Union.add(element)
+  - Parameterize Sequence/Union/Atom <Tok,Result>
+  - Make sure we never use raw types
+  - do Forest/Tree still need a Region?
 
-create( $c:{...}, class ) =
-  return create($c:{...})
+  - More topology untangling
 
-create( h:{...}, class ) = 
+  - tib: use the lexer only for indentation increases/decreases
 
-create( , String)
+  - grammar highlighting?
 
-create( _:{...}, String) = treat as char[]
-create( _:{...}, c[] )   = { create(.,c), create(.,c), ... }
-
-create( $c:{...} ) =
-
-
-  - clean up the visualization (?)
+  - copyright notices
 
-  - I still don't like Atom.Infer and Atom.Invert...
+  - tutorial
 
-  - better ambiguity debugging tools
+______________________________________________________________________________
+v1.1
 
-  - ParseFailed, GSS, Walk, Parser, Sequence, Forest
+  - Forest needs a "manual access" API
+      - the unwrap bit in Forest makes it really hard to expose an API for forests
 
-  - Fix the metagrammar (really?)
-      - evil problems with      (x y? z /ws)
+  - evil problems with      (x y? z /ws)
 
-  - copyright notices
-  - documentation
 
 ______________________________________________________________________________
 v1.1
@@ -43,8 +36,6 @@ v1.1
       - RFC2822 (email message/headers)
   - clean up the whole Walk situation (?)
 
-  - what if Tree<> could unwrap itself?
-
 
 ______________________________________________________________________________
 Soon
@@ -56,10 +47,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)