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

diff --git a/TODO b/TODO
index fd55d0b..2cec777 100644
--- a/TODO
+++ b/TODO
@@ -1,42 +1,42 @@
 _____________________________________________________________________________
 Immediately
 
-  - Performance
+- Migrate Demo.java -> MetaGrammar.java
+    - Figure out serialization
 
-     - Forest: keep() and valid() -- can we do this with states
-       rather than subtrees?
+- Clean up the prioritized-match garbage
+ - evil problems with      (x y? z /ws)
 
-     - hash Long->long: it's all bogus
 
-  * pick back up cleaning up end of Parser.java (Reduction)
+  - better ambiguity debugging tools / visualization
+  - ParseFailed, GSS, Walk, Parser, Sequence, Forest
+  - copyright notices
+  - documentation
 
-  - [more] sensible tree-printout
-
-  - revamp Tib.Block (do it all in the parser using indent/dedent?)
+______________________________________________________________________________
+v1.1
 
-  - 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
-
   - write some grammars
       - Java grammar
       - TeX (math?)
       - URL (RFC)
       - RFC2822 (email message/headers)
+  - clean up the whole Walk situation (?)
+
+  - what if Tree<> could unwrap itself?
 
 
 ______________________________________________________________________________
 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?
 
+  - 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
@@ -46,12 +46,12 @@ Soon
   - "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 +131,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