_____________________________________________________________________________
Immediately
- - Performance
-
- - Forest: keep() and valid() -- can we do this with states
- rather than subtrees?
-
- - hash Long->long: it's all bogus
+ - decent/better error messages
+ - fix the location stuff, it's broken
- * pick back up cleaning up end of Parser.java (Reduction)
+ - copyright notices
- - [more] sensible tree-printout
+ - documentation
- - revamp Tib.Block (do it all in the parser using indent/dedent?)
+______________________________________________________________________________
+v1.1
- - more natural phrasing of metagrammar?
- finalize metagrammar and rdp-op's
-
- - should Union.add() be there?
- - should Atom.top() be there?
-
- - decent/better error messages
- - fix the location stuff, it's broken
-
- write some grammars
- Java grammar
- TeX (math?)
- URL (RFC)
- RFC2822 (email message/headers)
+ - clean up the whole Walk situation (?)
______________________________________________________________________________
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
- "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