X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=93624048c6626dcab0820c84d8083997eec18c88;hp=27e96945a8f0d0ac0b45867a000d09e952215d35;hb=2c1c0293545f3d12c23220fd05c663e6aa3f3de1;hpb=f7dc68eeb40878c12463fc1ed2b4351b2a9fe261

diff --git a/TODO b/TODO
index 27e9694..9362404 100644
--- a/TODO
+++ b/TODO
@@ -1,58 +1,74 @@
 _____________________________________________________________________________
 Immediately
 
-  - finalize metagrammar and rdp-op's
+  - evil problems with: (x y? z /ws)
+     - it gets even more evil than that
+
+  - Annotation Tutorial
+
+  - MUST HAVE BETTER ERROR MESSAGES
+     - use for developing java15.g
+
+  - java15.g
 
-  - Lay down the law on the different kinds of Sequence productions
-    and how they work.
+  - topology no longer needed as an arg to parser
+  - expose parser's protected method?
 
-     => mydrop
-     => mylift
+  - do Forest/Tree still need a Region?
+  - copyright notices
+
+
+______________________________________________________________________________
+v1.1
 
-  - whitespace-in-braces?
-  - Deal with the problem of zero-rep productions and whitespace insertion
+  - More topology untangling [later]
+  - tib: use the lexer only for indentation increases/decreases
+  - grammar highlighting?
 
-  - switch maximal to not-followed-by (~/~)
+  - 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?
 
-  - fix the location stuff, it's broken
-  - decent/better error messages
 
+______________________________________________________________________________
+v1.1
+
+  - finalize metagrammar and rdp-op's
   - write some grammars
       - Java grammar
       - TeX (math?)
       - URL (RFC)
       - RFC2822 (email message/headers)
-      - Wiki grammar
+  - clean up the whole Walk situation (?)
+
 
 ______________________________________________________________________________
 Soon
 
-  - clean up the whole Walk situation
+  - serialization of parse tables
 
-  - cleaner solution to "maximal"?
+  - "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
 
+  - Partly-Linear-PATR? (O(n^6) unification grammar)
+
   - Implement a k-token peek buffer (for each state, see if it "dead
     ends" during the next k Phases based solely on state -- ignoring
     result SPPF)
@@ -64,11 +80,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
@@ -131,3 +142,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