X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=93624048c6626dcab0820c84d8083997eec18c88;hp=1e53bb83803c4c468679d4feecd2e18fc61b6032;hb=2c1c0293545f3d12c23220fd05c663e6aa3f3de1;hpb=e5cfb136bf7fd1352eff1bd87a458aa4ff748537

diff --git a/TODO b/TODO
index 1e53bb8..9362404 100644
--- a/TODO
+++ b/TODO
@@ -1,32 +1,34 @@
 _____________________________________________________________________________
 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
+  - evil problems with: (x y? z /ws)
+     - it gets even more evil than that
 
-create( $c:{...}, class ) =
-  return create($c:{...})
+  - Annotation Tutorial
 
-create( h:{...}, class ) = 
+  - MUST HAVE BETTER ERROR MESSAGES
+     - use for developing java15.g
 
-create( , String)
+  - java15.g
 
-create( _:{...}, String) = treat as char[]
-create( _:{...}, c[] )   = { create(.,c), create(.,c), ... }
+  - topology no longer needed as an arg to parser
+  - expose parser's protected method?
+
+  - do Forest/Tree still need a Region?
+  - copyright notices
 
-create( $c:{...} ) =
 
+______________________________________________________________________________
+v1.1
 
-  - better ambiguity debugging tools / visualization
+  - More topology untangling [later]
+  - tib: use the lexer only for indentation increases/decreases
+  - grammar highlighting?
 
-  - 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)
 
-  - copyright notices
-  - documentation
 
 ______________________________________________________________________________
 v1.1
@@ -39,8 +41,6 @@ v1.1
       - RFC2822 (email message/headers)
   - clean up the whole Walk situation (?)
 
-  - what if Tree<> could unwrap itself?
-
 
 ______________________________________________________________________________
 Soon
@@ -52,10 +52,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)