X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=5f5e1cf6546399a5c3e34f45890b9f2bae1024a4;hp=78baf0190bfcc2c917c6ac3e0a612001155201a8;hb=7783442fcff4e640ecdcbdb6149463048d32f7a7;hpb=ea5d0a5e3dffb5ba0143179fd28608c2de8046e0

diff --git a/TODO b/TODO
index 78baf01..5f5e1cf 100644
--- a/TODO
+++ b/TODO
@@ -1,29 +1,35 @@
-
-______________________________________________________________________________
+_____________________________________________________________________________
 Immediately
 
-  - switch maximal to not-followed-by (~/~)
+  - Sensible tree-printout
+  - make Tib.Block extend Tree<>
+
+  - more natural phrasing of metagrammar?
+
+  - finalize metagrammar and rdp-op's
+
+  - Deal with the problem of zero-rep productions and whitespace insertion
 
   - should Union.add() be there?
   - should Atom.top() be there?
 
   - fix the location stuff, it's broken
   - decent/better error messages
+      - substring parsing required
 
   - write some grammars
       - Java grammar
       - TeX (math?)
       - URL (RFC)
       - RFC2822 (email message/headers)
-      - Wiki grammar
+
+  - PL-PATR?
 
 ______________________________________________________________________________
 Soon
 
   - clean up the whole Walk situation
 
-  - cleaner solution to "maximal"?
-
   - "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
@@ -33,6 +39,13 @@ 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?
+
 ______________________________________________________________________________
 Later
 
@@ -47,11 +60,6 @@ Later
     nodes which are transient in the sense that they have only one
     eligible reduction?
 
-  - Implement "GLR syntactic predicates" -- the ability to do
-    arbitrary lookahead (ie "followed-by" and "not-followed-by" for
-    arbitrary patterns).  This enables generalized longest-match and
-    lets us drop the Maximal hack.
-
   - Re-read Rekers, particularly the stuff on optimal sharing
 
   - Isolate the Element objects from Parse.Table/GSS so we can move
@@ -108,3 +116,9 @@ Later
   - implement Johnstone's algorithm for "reduced, resolved LR
     tables" to eliminate superfluous reductions on
     epsilon-transitions.
+
+______________________________________________________________________________
+Neat Ideas
+
+  - Rekers & Koorn note that GLR Substring Parsing can be used to do
+    really elegant and generalized "autocompletion".