_____________________________________________________________________________
Immediately
- - I still don't like Atom.Infer and Atom.Invert...
+ - evil problems with: (x y? z /ws)
+ - it gets even more evil than that
- - better ambiguity debugging tools
+ - Annotation Tutorial
- - ParseFailed, GSS, Walk, Parser, Sequence, Forest
+ - MUST HAVE BETTER ERROR MESSAGES
+ - when ambiguity encountered, show text region (where-to-where)
+ - use for developing java15.g
- - Fix the metagrammar (really?)
- - evil problems with (x y? z /ws)
+ - java15.g
+ - topology no longer needed as an arg to parser
+ - expose parser's protected method?
+
+ - do Forest/Tree still need a Region?
- copyright notices
- - documentation
+
+
+______________________________________________________________________________
+v1.1
+
+ - broader regression testing (for stuff like error messages, etc)
+
+ - More topology untangling [later]
+ - tib: use the lexer only for indentation increases/decreases
+ - grammar highlighting?
+
+ - Forest needs a "manual access" API
+ - the unwrap bit in Forest makes it really hard to expose an API for forests
+
+
______________________________________________________________________________
v1.1
- RFC2822 (email message/headers)
- clean up the whole Walk situation (?)
- - what if Tree<> could unwrap itself?
-
______________________________________________________________________________
Soon
- 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
- if we need to be able to do lift operations on it.
- Parameterized LR
- "Regular Right Part" grammars (NP Chapman, etc)