_____________________________________________________________________________
Immediately
- - evil problems with: (x y? z /ws)
- - it gets even more evil than that
-
+ - comparison test is probably chewing up most of the time
+
+ - Check if the only remaining stack is lame (hopeful/nothopeful)
+ - write a testcase for this
+ - circular gramars
+ s = A
+ A = A | "b"
+ - foo.add(x)
+ foo.add(y.andnot(x)) ==> this is broken
- Annotation Tutorial
- - MUST HAVE BETTER ERROR MESSAGES
- - when ambiguity encountered, show text region (where-to-where)
- - use for developing java15.g
-
- - 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
+ ..................................................
+ - serializable parse tables?
+ - Treewalker code compiler?
______________________________________________________________________________
v1.1
+ - precedes restrictions ("<-")
+ - MUST HAVE BETTER ERROR MESSAGES
+ - use for developing java15.g
+ - java15.g
+ - once this is ready, do big announcement
- 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
+v1.2
- finalize metagrammar and rdp-op's
- write some grammars
______________________________________________________________________________
Later
+ - understand and implement the RNGLR "kernel state" optimization.
+ The _Practical Early Parsing_ paper may help.
+
- Partly-Linear-PATR? (O(n^6) unification grammar)
- Implement a k-token peek buffer (for each state, see if it "dead
projects / sbp.git / blobdiff