X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=086144069099564c006e464e145809ec426ecd78;hp=d03ba8a14459ddacecd96609cc95531ec79c0947;hb=972303162555284f8066047d3caead8df139afd4;hpb=c366dacc334fe2e35835164f5a37d3eebb2ca6d5 diff --git a/TODO b/TODO index d03ba8a..0861440 100644 --- a/TODO +++ b/TODO @@ -1,54 +1,89 @@ _____________________________________________________________________________ Immediately - - Performance - - hash Long->long: it's all bogus + - Check if the only remaining stack is lame + - write a testcase for this - * pick back up cleaning up end of Parser.java (Reduction) + - circular gramars + s = A + A = A | "b" - - [more] sensible tree-printout + - foo.add(x) + foo.add(y.andnot(x)) ==> this is broken - - revamp Tib.Block (do it all in the parser using indent/dedent?) + - Annotation Tutorial - - more natural phrasing of metagrammar? - - finalize metagrammar and rdp-op's + .................................................. + + - 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 - - decent/better error messages - - fix the location stuff, it's broken + - 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 + + + +______________________________________________________________________________ +v1.2 + - finalize metagrammar and rdp-op's - 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? - - "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. + - substring parsing for better error messages - Parameterized LR - "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? + + - Labeled edges on trees (associate a label with each slot in the + child array in Forest.Body? might make equality tough) -- + equivalent to Feature Structures. Colon-labeling. ______________________________________________________________________________ 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