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

diff --git a/TODO b/TODO
index 0ec9353..1e53bb8 100644
--- a/TODO
+++ b/TODO
@@ -1,38 +1,57 @@
 _____________________________________________________________________________
 Immediately
 
-  - finalize metagrammar and rdp-op's
+- If a top-level rule has labels but no head-tag, like this
+    Foo = a:Bar b:Baz
+  then infer the name of the rule it belongs to
+
+create( $c:{...}, class ) =
+  return create($c:{...})
+
+create( h:{...}, class ) = 
+
+create( , String)
+
+create( _:{...}, String) = treat as char[]
+create( _:{...}, c[] )   = { create(.,c), create(.,c), ... }
+
+create( $c:{...} ) =
 
-  - Lay down the law on the different kinds of Sequence productions
-    and how they work.
 
-     => mydrop
-     => mylift
+  - better ambiguity debugging tools / visualization
 
-  - Deal with the problem of zero-rep productions and whitespace insertion
+  - ParseFailed, GSS, Walk, Parser, Sequence, Forest
 
-  - switch maximal to not-followed-by (~/~)
+  - Fix the metagrammar (really?)
+      - evil problems with      (x y? z /ws)
 
-  - should Union.add() be there?
-  - should Atom.top() be there?
+  - copyright notices
+  - documentation
 
-  - 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 (?)
+
+  - what if Tree<> could unwrap itself?
+
 
 ______________________________________________________________________________
 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?
 
+  - 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
@@ -42,16 +61,18 @@ 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
 
+  - 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)
@@ -63,11 +84,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
@@ -130,3 +146,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