X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=93624048c6626dcab0820c84d8083997eec18c88;hp=f059a77b4fd96ab9c8abf7dd9e4c29df20cad354;hb=2c1c0293545f3d12c23220fd05c663e6aa3f3de1;hpb=0ab024f487647f99eb000345c29c2f8e9b52a200 diff --git a/TODO b/TODO index f059a77..9362404 100644 --- a/TODO +++ b/TODO @@ -1,17 +1,34 @@ _____________________________________________________________________________ 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 + - 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 + + - 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 @@ -24,8 +41,6 @@ v1.1 - RFC2822 (email message/headers) - clean up the whole Walk situation (?) - - what if Tree<> could unwrap itself? - ______________________________________________________________________________ Soon @@ -37,10 +52,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)