X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=e3e7dfa9c9b6d098e980522e73bb90ec4d136e07;hp=1d628025dfb76a84c08b695ad58aacc26f7c6650;hb=4aadad134578c7f1f450f426c3717bc20adcd8ea;hpb=d684010debf9069af108981d9451932c15b1ec75 diff --git a/TODO b/TODO index 1d62802..e3e7dfa 100644 --- a/TODO +++ b/TODO @@ -1,16 +1,45 @@ _____________________________________________________________________________ Immediately - - decent/better error messages - - fix the location stuff, it's broken + - foo.add(x) + foo.add(y.andnot(x)) ==> this is broken - - copyright notices + - Annotation Tutorial - - documentation + .................................................. + + - 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 + + + +______________________________________________________________________________ +v1.2 + - finalize metagrammar and rdp-op's - write some grammars - Java grammar @@ -30,10 +59,6 @@ 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) @@ -42,6 +67,9 @@ Soon - inference of rejections for literals - "prefer whitespace higher up" (?) + - 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