checkpoint

[sbp.git] / TODO

diff --git a/TODO b/TODO
index fd55d0b..1e53bb8 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,42 +1,57 @@
 _____________________________________________________________________________
 Immediately
 
-  - Performance
+- 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
 
-     - Forest: keep() and valid() -- can we do this with states
-       rather than subtrees?
+create( $c:{...}, class ) =
+  return create($c:{...})
 
-     - hash Long->long: it's all bogus
+create( h:{...}, class ) = 
 
-  * pick back up cleaning up end of Parser.java (Reduction)
+create( , String)
 
-  - [more] sensible tree-printout
+create( _:{...}, String) = treat as char[]
+create( _:{...}, c[] )   = { create(.,c), create(.,c), ... }
 
-  - revamp Tib.Block (do it all in the parser using indent/dedent?)
+create( $c:{...} ) =
 
-  - more natural phrasing of metagrammar?
-  - finalize metagrammar and rdp-op's
 
-  - should Union.add() be there?
-  - should Atom.top() be there?
+  - better ambiguity debugging tools / visualization
+
+  - ParseFailed, GSS, Walk, Parser, Sequence, Forest
+
+  - Fix the metagrammar (really?)
+      - evil problems with      (x y? z /ws)
 
-  - decent/better error messages
-      - fix the location stuff, it's broken
+  - copyright notices
+  - documentation
 
+______________________________________________________________________________
+v1.1
+
+  - finalize metagrammar and rdp-op's
   - 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 +61,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 +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