X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=086144069099564c006e464e145809ec426ecd78;hp=d7afed210b1b4c08633226d90b5e1fededf516d4;hb=1d6f5a5f585a993cb780ea454fa1bd26d440c4ce;hpb=45d799349e635f1a99e3974e4504a43d5a7aaf33

diff --git a/TODO b/TODO
index d7afed2..0861440 100644
--- a/TODO
+++ b/TODO
@@ -1,39 +1,51 @@
 _____________________________________________________________________________
 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
+  - Check if the only remaining stack is lame
+    - write a testcase for this
 
-create( $c:{...}, class ) =
-  return create($c:{...})
+  - circular gramars
+      s = A
+      A = A | "b"
 
-create( h:{...}, class ) = 
+  - foo.add(x)
+    foo.add(y.andnot(x)) ==> this is broken
 
-create( , String)
+  - Annotation Tutorial
 
-create( _:{...}, String) = treat as char[]
-create( _:{...}, c[] )   = { create(.,c), create(.,c), ... }
+  ..................................................
 
-create( $c:{...} ) =
+  - evil problems with: (x y? z /ws)
+     - it gets even more evil than that
+     - basically, follow restrictions are not honored when the element
+       matches against the empty string
 
+______________________________________________________________________________
+v1.1
+
+  - precedes restrictions ("<-")
+
+  - MUST HAVE BETTER ERROR MESSAGES
+     - use for developing java15.g
 
-  - clean up the visualization (?)
+  - java15.g
+     - once this is ready, do big announcement
 
-  - I still don't like Atom.Infer and Atom.Invert...
+  - topology no longer needed as an arg to parser?
 
-  - better ambiguity debugging tools
+  - broader regression testing (for stuff like error messages, etc)
 
-  - ParseFailed, GSS, Walk, Parser, Sequence, Forest
+  - More topology untangling [later]
+  - tib: use the lexer only for indentation increases/decreases
+  - grammar highlighting?
+
+  - 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
+v1.2
 
   - finalize metagrammar and rdp-op's
   - write some grammars
@@ -43,8 +55,6 @@ v1.1
       - RFC2822 (email message/headers)
   - clean up the whole Walk situation (?)
 
-  - what if Tree<> could unwrap itself?
-
 
 ______________________________________________________________________________
 Soon
@@ -56,10 +66,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)
@@ -75,6 +81,9 @@ Soon
 ______________________________________________________________________________
 Later
 
+  - understand and implement the RNGLR "kernel state" optimization.
+    The _Practical Early Parsing_ paper may help.
+
   - Partly-Linear-PATR? (O(n^6) unification grammar)
 
   - Implement a k-token peek buffer (for each state, see if it "dead