X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;ds=sidebyside;f=TODO;h=5522eab55abc0024a1884d17ec52a6aade678e46;hb=b320f26b6e2cc13dcfcd810c7d5b507b942e8c70;hp=f059a77b4fd96ab9c8abf7dd9e4c29df20cad354;hpb=0ab024f487647f99eb000345c29c2f8e9b52a200;p=sbp.git diff --git a/TODO b/TODO index f059a77..5522eab 100644 --- a/TODO +++ b/TODO @@ -1,18 +1,27 @@ _____________________________________________________________________________ Immediately - - I still don't like Atom.Infer and Atom.Invert... + - Topology crap is kinda messed up + - Atom should be a topology, shouldn't it? - - better ambiguity debugging tools + - needs/hates/follow API ugliness - - ParseFailed, GSS, Walk, Parser, Sequence, Forest - - - Fix the metagrammar (really?) - - evil problems with (x y? z /ws) + - 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 - copyright notices - documentation + - grammar highlighting? + - comment indentation vs block indentation? + - { and } in
+  - recursive { { foo } }
+
 ______________________________________________________________________________
 v1.1
 
@@ -24,8 +33,6 @@ v1.1
       - RFC2822 (email message/headers)
   - clean up the whole Walk situation (?)
 
-  - what if Tree<> could unwrap itself?
-
 
 ______________________________________________________________________________
 Soon
@@ -37,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)