X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=d03ba8a14459ddacecd96609cc95531ec79c0947;hp=fd55d0bac1fccf1994c5540ab188f4b6e2caa203;hb=c366dacc334fe2e35835164f5a37d3eebb2ca6d5;hpb=03dd839af8e8d1a6c2f69c5410da6d19fbbe3931;ds=inline

diff --git a/TODO b/TODO
index fd55d0b..d03ba8a 100644
--- a/TODO
+++ b/TODO
@@ -2,10 +2,6 @@ _____________________________________________________________________________
 Immediately
 
   - Performance
-
-     - Forest: keep() and valid() -- can we do this with states
-       rather than subtrees?
-
      - hash Long->long: it's all bogus
 
   * pick back up cleaning up end of Parser.java (Reduction)
@@ -17,9 +13,6 @@ Immediately
   - more natural phrasing of metagrammar?
   - finalize metagrammar and rdp-op's
 
-  - should Union.add() be there?
-  - should Atom.top() be there?
-
   - decent/better error messages
       - fix the location stuff, it's broken
 
@@ -131,3 +124,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