X-Git-Url: http://git.megacz.com/?p=sbp.git;a=blobdiff_plain;f=TODO;h=8c3fdf98276d69cc7d3bd723fd84aaeae3357602;hp=1e53bb83803c4c468679d4feecd2e18fc61b6032;hb=ae0cef03f2e46f6ae6438f9a3e60ca36ff1a4643;hpb=e5cfb136bf7fd1352eff1bd87a458aa4ff748537 diff --git a/TODO b/TODO index 1e53bb8..8c3fdf9 100644 --- a/TODO +++ b/TODO @@ -1,33 +1,27 @@ _____________________________________________________________________________ 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 + - needs/hates/follow API ugliness -create( $c:{...}, class ) = - return create($c:{...}) + - Topology crap is kinda messed up + - Atom should be a topology, shouldn't it? -create( h:{...}, class ) = - -create( , String) - -create( _:{...}, String) = treat as char[] -create( _:{...}, c[] ) = { create(.,c), create(.,c), ... } - -create( $c:{...} ) = - - - - better ambiguity debugging tools / visualization + - 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
 
@@ -39,8 +33,6 @@ v1.1
       - RFC2822 (email message/headers)
   - clean up the whole Walk situation (?)
 
-  - what if Tree<> could unwrap itself?
-
 
 ______________________________________________________________________________
 Soon
@@ -52,10 +44,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)