X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;ds=inline;f=TODO;h=5522eab55abc0024a1884d17ec52a6aade678e46;hb=173e1696d10a91db6f5a919dbb2b2ed2c6e2a227;hp=c7ad150a242c07c529b5ec58bbbccdae6117e708;hpb=ebb5fe5647046306f415e31e4967b23169c9004e;p=sbp.git diff --git a/TODO b/TODO index c7ad150..5522eab 100644 --- a/TODO +++ b/TODO @@ -1,57 +1,60 @@ _____________________________________________________________________________ Immediately - - Performance + - Topology crap is kinda messed up + - Atom should be a topology, shouldn't it? - - Forest: keep() and valid() -- can we do this with states - rather than subtrees? + - needs/hates/follow API ugliness - - hash Long->long: it's all bogus + - 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 - * pick back up cleaning up end of Parser.java (Reduction) + - evil problems with (x y? z /ws) + - ParseFailed, GSS, Walk, Parser, Sequence, Forest + - copyright notices + - documentation - - [more] sensible tree-printout + - grammar highlighting? + - comment indentation vs block indentation? + - { and } in
+ - recursive { { foo } } - - revamp Tib.Block (do it all in the parser using indent/dedent?) +______________________________________________________________________________ +v1.1 - - more natural phrasing of metagrammar? - finalize metagrammar and rdp-op's - - - should Union.add() be there? - - should Atom.top() be there? - - - decent/better error messages - - fix the location stuff, it's broken - - write some grammars - Java grammar - TeX (math?) - URL (RFC) - RFC2822 (email message/headers) + - clean up the whole Walk situation (?) ______________________________________________________________________________ Soon - - substring parsing for better error messages + - serialization of parse tables - - clean up the whole Walk situation + - "ambiguity modulo dropped fragments"? + - can this be checked statically? + - eliminated statically? - - "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. + - substring parsing for better error messages - Parameterized LR - "Regular Right Part" grammars (NP Chapman, etc) - Attribute unification - - serialization of parse tables - inference of rejections for literals - "prefer whitespace higher up" (?) - - "ambiguity modulo dropped fragments"? - - can this be checked statically? - - eliminated statically? + + - Labeled edges on trees (associate a label with each slot in the + child array in Forest.Body? might make equality tough) -- + equivalent to Feature Structures. Colon-labeling. ______________________________________________________________________________ Later