X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=0ec93530ed77c6537f41ea9f0cb9fb1f7326554c;hp=118520951f00698612b7fb4c1cb1d2465e597861;hb=50ff66e926f981a5b3716f218ad24603c2a12e3f;hpb=77d1e5fd29be1ca529e71a4c011f5edea61588e8

diff --git a/TODO b/TODO
index 1185209..0ec9353 100644
--- a/TODO
+++ b/TODO
@@ -1,37 +1,16 @@
-// priorities are all messy and dont get serialized
-// 1. Error messages
-// 2. Java MetaGrammar (proof of concept)
-// 3. Ivan's MetaGrammar
-// 4. Documentation format
-//       - TIB
-
-// TODO: better API for interfacing with Java
-// TODO: error messages
-// TODO: integrate with TIB
-
-// Element
-// Walk
-// ParseTable / GSS
-// MetaGrammar (necessary/relevant?)
-// Tree<String> (cleanup?)
-// Union.SubUnion
-// Repeat
-
-// FEATURE: serialization of ParseTable's, generation of Java code
-// FEATURE: infer reject elements for literals
-// FEATURE: prefer whitespace higher up
-// FEATURE: full conjunctive and boolean grammars
-// FEATURE: "ambiguity modulo dropped fragments"?  can this be checked for statically?  eliminated statically?
-//            - drop stuff during the parsing process (drop nodes)
-
-// LATER: Element<A> -- parameterize over the input token type?  Makes a huge mess...
-// LATER: Go back to where Sequence is not an Element?
-//            - The original motivation for making Sequence "first class" was the fact that 
-//              in order to do associativity right you need to have per-Sequence follow sets
-
-______________________________________________________________________________
+_____________________________________________________________________________
 Immediately
 
+  - finalize metagrammar and rdp-op's
+
+  - Lay down the law on the different kinds of Sequence productions
+    and how they work.
+
+     => mydrop
+     => mylift
+
+  - Deal with the problem of zero-rep productions and whitespace insertion
+
   - switch maximal to not-followed-by (~/~)
 
   - should Union.add() be there?
@@ -63,6 +42,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
 
@@ -138,3 +124,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".