_____________________________________________________________________________
Immediately
- - Sensible tree-printout
- - make Tib.Block extend Tree<>
+ * pick back up cleaning up end of Parser.java (Reduction)
- - more natural phrasing of metagrammar?
-
- - finalize metagrammar and rdp-op's
+ - [more] sensible tree-printout
- - Deal with the problem of zero-rep productions and whitespace insertion
+ - revamp Tib.Block (do it all in the parser using indent/dedent?)
- - should Union.add() be there?
- - should Atom.top() be there?
+ - more natural phrasing of metagrammar?
+ - finalize metagrammar and rdp-op's
- - fix the location stuff, it's broken
- decent/better error messages
- - substring parsing required
+ - fix the location stuff, it's broken
- write some grammars
- Java grammar
- URL (RFC)
- RFC2822 (email message/headers)
- - PL-PATR?
______________________________________________________________________________
Soon
+ - substring parsing for better error messages
+
- clean up the whole Walk situation
- "lift" cases:
______________________________________________________________________________
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)
- 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