X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=cecd2d440811bf4c47f6bb548edf6fc6d49f9678;hp=fd55d0bac1fccf1994c5540ab188f4b6e2caa203;hb=75d0fa39d405292f4b831a6d1743f2aeea01ebd4;hpb=03dd839af8e8d1a6c2f69c5410da6d19fbbe3931

diff --git a/TODO b/TODO
index fd55d0b..cecd2d4 100644
--- a/TODO
+++ b/TODO
@@ -1,57 +1,63 @@
 _____________________________________________________________________________
 Immediately
 
-  - Performance
+  - Sequence extends Element (?) -> then add Union.add(element)
+  - Parameterize Sequence/Union/Atom <Tok,Result>
+  - Make sure we never use raw types
+  - do Forest/Tree still need a Region?
 
-     - Forest: keep() and valid() -- can we do this with states
-       rather than subtrees?
+  - More topology untangling
 
-     - hash Long->long: it's all bogus
+  - tib: use the lexer only for indentation increases/decreases
 
-  * pick back up cleaning up end of Parser.java (Reduction)
+  - grammar highlighting?
 
-  - [more] sensible tree-printout
+  - copyright notices
 
-  - revamp Tib.Block (do it all in the parser using indent/dedent?)
+  - tutorial
 
-  - more natural phrasing of metagrammar?
-  - finalize metagrammar and rdp-op's
+______________________________________________________________________________
+v1.1
+
+  - 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?
+  - evil problems with      (x y? z /ws)
 
-  - decent/better error messages
-      - fix the location stuff, it's broken
 
+______________________________________________________________________________
+v1.1
+
+  - 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
@@ -131,3 +137,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