X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=31dbd1d1590926d988667c4c42442289326ec8aa;hp=d7afed210b1b4c08633226d90b5e1fededf516d4;hb=189d68c64f7aaec90b7cdef0fb2c358fe4f0dd21;hpb=45d799349e635f1a99e3974e4504a43d5a7aaf33 diff --git a/TODO b/TODO index d7afed2..31dbd1d 100644 --- a/TODO +++ b/TODO @@ -1,37 +1,25 @@ _____________________________________________________________________________ Immediately -- If a top-level rule has labels but no head-tag, like this - Foo = a:Bar b:Baz - then infer the name of the rule it belongs to + * we can nuke Atom.toAtom() now! + - Topology crap is kinda messed up -create( $c:{...}, class ) = - return create($c:{...}) - -create( h:{...}, class ) = - -create( , String) - -create( _:{...}, String) = treat as char[] -create( _:{...}, c[] ) = { create(.,c), create(.,c), ... } - -create( $c:{...} ) = - - - - clean up the visualization (?) - - - I still don't like Atom.Infer and Atom.Invert... - - - better ambiguity debugging tools + - do Forest/Tree still need a Region? + - reconsider the degree of genericization + - GraphViz stuff pollutes the API... + - 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 @@ -43,8 +31,6 @@ v1.1 - RFC2822 (email message/headers) - clean up the whole Walk situation (?) - - what if Tree<> could unwrap itself? - ______________________________________________________________________________ Soon @@ -56,10 +42,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)