X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=280f8755da14c15570630db831e30dc9eda1de33;hp=f059a77b4fd96ab9c8abf7dd9e4c29df20cad354;hb=df2dac17a58713dd1e3fba3101666bea7cb6f561;hpb=0ab024f487647f99eb000345c29c2f8e9b52a200

diff --git a/TODO b/TODO
index f059a77..280f875 100644
--- a/TODO
+++ b/TODO
@@ -1,21 +1,47 @@
 _____________________________________________________________________________
 Immediately
 
-  - I still don't like Atom.Infer and Atom.Invert...
+  - foo.add(x)
+    foo.add(y.andnot(x)) ==> this is broken
 
-  - better ambiguity debugging tools
+  - Annotation Tutorial
 
-  - ParseFailed, GSS, Walk, Parser, Sequence, Forest
+  - Get at least *some* sort of moderate improvement in the error messages
 
-  - Fix the metagrammar (really?)
-      - evil problems with      (x y? z /ws)
+  ..................................................
 
-  - copyright notices
-  - documentation
+  - 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
+
+  - java15.g
+     - once this is ready, do big announcement
+
+  - topology no longer needed as an arg to parser?
+
+  - broader regression testing (for stuff like error messages, etc)
+
+  - 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
+
+
+
+______________________________________________________________________________
+v1.2
+
   - finalize metagrammar and rdp-op's
   - write some grammars
       - Java grammar
@@ -24,8 +50,6 @@ v1.1
       - RFC2822 (email message/headers)
   - clean up the whole Walk situation (?)
 
-  - what if Tree<> could unwrap itself?
-
 
 ______________________________________________________________________________
 Soon
@@ -37,10 +61,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)