Tree.java: resolve any lifting at Tree-creation time

[sbp.git] / TODO

diff --git a/TODO b/TODO
index b383c90..ed981e8 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,57 +1,78 @@
 _____________________________________________________________________________
 Immediately
 
-  - Performance
-     - hash Long->long: it's all bogus
+  - comparison test is probably chewing up most of the time
 
-  * pick back up cleaning up end of Parser.java (Reduction)
+  - Check if the only remaining stack is lame (hopeful/nothopeful)
+    - write a testcase for this
+  - circular gramars
+      s = A
+      A = A | "b"
+  - foo.add(x)
+    foo.add(y.andnot(x)) ==> this is broken
+  - Annotation Tutorial
 
-  - [more] sensible tree-printout
+  ..................................................
 
-  - revamp Tib.Block (do it all in the parser using indent/dedent?)
+  - serializable parse tables?
+  - Treewalker code compiler?
 
-  - more natural phrasing of metagrammar?
-  - finalize metagrammar and rdp-op's
+______________________________________________________________________________
+v1.1
+
+  - precedes restrictions ("<-")
+  - MUST HAVE BETTER ERROR MESSAGES
+     - use for developing java15.g
+  - java15.g
+     - once this is ready, do big announcement
+  - broader regression testing (for stuff like error messages, etc)
+  - More topology untangling [later]
+  - grammar highlighting?
+  - Forest needs a "manual access" API
+      - the unwrap bit in Forest makes it really hard to expose an API for forests
 
-  - should Union.add() be there?
-  - should Atom.top() be there?
 
-  - decent/better error messages
-      - fix the location stuff, it's broken
 
+______________________________________________________________________________
+v1.2
+
+  - finalize metagrammar and rdp-op's
   - write some grammars
       - Java grammar
       - TeX (math?)
       - URL (RFC)
       - RFC2822 (email message/headers)
+  - clean up the whole Walk situation (?)
 
 
 ______________________________________________________________________________
 Soon
 
-  - substring parsing for better error messages
+  - serialization of parse tables
 
-  - clean up the whole Walk situation
+  - "ambiguity modulo dropped fragments"?
+       - can this be checked statically?
+       - eliminated statically?
 
-  - "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.
+  - substring parsing for better error messages
 
   - Parameterized LR
   - "Regular Right Part" grammars (NP Chapman, etc)
   - Attribute unification
 
-  - serialization of parse tables
   - inference of rejections for literals
   - "prefer whitespace higher up" (?)
-  - "ambiguity modulo dropped fragments"?
-       - can this be checked statically?
-       - eliminated statically?
+
+  - Labeled edges on trees (associate a label with each slot in the
+    child array in Forest.Body?  might make equality tough) --
+    equivalent to Feature Structures.  Colon-labeling.
 
 ______________________________________________________________________________
 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