X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;ds=inline;f=TODO;h=7186baf093e0b8347d9e414c22876c32a0fdcd5d;hb=d86c2344f6f5b958d56e2aa55e84af2dc76ab487;hp=f059a77b4fd96ab9c8abf7dd9e4c29df20cad354;hpb=0ab024f487647f99eb000345c29c2f8e9b52a200;p=sbp.git diff --git a/TODO b/TODO index f059a77..7186baf 100644 --- a/TODO +++ b/TODO @@ -1,18 +1,20 @@ _____________________________________________________________________________ Immediately - - I still don't like Atom.Infer and Atom.Invert... - - - better ambiguity debugging tools + - do Forest/Tree still need a Region? + - 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 - - - Fix the metagrammar (really?) - - evil problems with (x y? z /ws) - - copyright notices - documentation + - grammar highlighting? + - comment indentation vs block indentation? + - { and } in
+ - recursive { { foo } } + ______________________________________________________________________________ v1.1 @@ -24,8 +26,6 @@ v1.1 - RFC2822 (email message/headers) - clean up the whole Walk situation (?) - - what if Tree<> could unwrap itself? - ______________________________________________________________________________ Soon @@ -37,10 +37,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)