X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=b720e81803213196ce68018c1bd08a467a74b755;hp=5f5e1cf6546399a5c3e34f45890b9f2bae1024a4;hb=bc150ec13ece2f6c8fb47cf5b81f2b01fce9c0a6;hpb=5252cc15c0d998517bf566229cd0c9d04dcff348

diff --git a/TODO b/TODO
index 5f5e1cf..b720e81 100644
--- a/TODO
+++ b/TODO
@@ -1,54 +1,85 @@
 _____________________________________________________________________________
 Immediately
+// use 'a'-'z' or 'a-z' instead of [a-z]?
+// EOF token?
+// #include (with renaming?)
 
-  - Sensible tree-printout
-  - make Tib.Block extend Tree<>
+  - de-genericize?
 
-  - more natural phrasing of metagrammar?
+  - better toString() methods all around...
 
-  - finalize metagrammar and rdp-op's
+  - cleanup: Forest, ParseFailed, Parser, Union, (just a bit: GSS,Node)
+
+  - circular gramars?
+      s = A
+      A = A | "b"
+  - foo.add(x)
+    foo.add(y.andnot(x)) ==> this is broken
+  - Annotation Tutorial
+
+  ..................................................
+
+  - serializable parse tables?
+  - Treewalker code compiler?
+
+______________________________________________________________________________
+v1.1
 
-  - Deal with the problem of zero-rep productions and whitespace insertion
+  - 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?
 
-  - fix the location stuff, it's broken
-  - decent/better error messages
-      - substring parsing required
 
+______________________________________________________________________________
+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 (?)
 
-  - PL-PATR?
 
 ______________________________________________________________________________
 Soon
 
-  - clean up the whole Walk situation
+  - serialization of parse tables
+
+  - "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
     ends" during the next k Phases based solely on state -- ignoring
     result SPPF)
@@ -122,3 +153,17 @@ Neat Ideas
 
   - Rekers & Koorn note that GLR Substring Parsing can be used to do
     really elegant and generalized "autocompletion".
+
+
+______________________________________________________________________________
+Ideas for the Future
+
+- Incremental parse table construction
+- "lazy GLR" and "lazy trees" -> language with first-class CF matching
+    - perhaps linear boolean grammars instead? (linear time, quad space)
+- Forest parsing => chained parsers
+- unification parsing, attributes, etc
+- RRP grammars?
+- Take another stab at maximal-match?  Nonterminal not-followed-by is
+  too strong.
+- Error recovery based on substring parsing