X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=086144069099564c006e464e145809ec426ecd78;hp=d58eb06ef9389c940956de251ed50049cd4b89f1;hb=a8478f5ddfbfbc8d910d09f27163cbd55752d3b6;hpb=280e93a7eec101178dc81f8009eedb2916271f09 diff --git a/TODO b/TODO index d58eb06..0861440 100644 --- a/TODO +++ b/TODO @@ -1,24 +1,51 @@ _____________________________________________________________________________ Immediately - - do Forest/Tree still need a Region? - - reconsider the degree of genericization - - GraphViz stuff pollutes the API... + - Check if the only remaining stack is lame + - 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 + + .................................................. + + - evil problems with: (x y? z /ws) + - it gets even more evil than that + - basically, follow restrictions are not honored when the element + matches against the empty string + +______________________________________________________________________________ +v1.1 + + - precedes restrictions ("<-") + + - MUST HAVE BETTER ERROR MESSAGES + - use for developing java15.g + + - java15.g + - once this is ready, do big announcement + + - topology no longer needed as an arg to parser? + + - 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 - - evil problems with (x y? z /ws) - - ParseFailed, GSS, Walk, Parser, Sequence, Forest - - copyright notices - - documentation - - grammar highlighting? - - comment indentation vs block indentation? - - { and } in
-  - recursive { { foo } }
 
 ______________________________________________________________________________
-v1.1
+v1.2
 
   - finalize metagrammar and rdp-op's
   - write some grammars
@@ -54,6 +81,9 @@ Soon
 ______________________________________________________________________________
 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