On Thu, May 08, 2014 at 03:15:20PM -0700, Cirilo Bernardo wrote: > The question is: what is really needed and how can it be implemented?
Storing a whole sexp would be done with the DOM model or something similar (DOM is not exactly the best way to handle a sexp, but at least it's already done:P) As for the really needed it's that or only a user property bag; AFAIK there is not a way to meaningfully store only 'a piece' of a sexp: given the recursive nature of the thing, 'a piece' would quickly converge to the whole expression. While not really elegant, if performance actually is a problem (Dick seems really bothered by that) you could use the current parser for standard data and DOM for the extensions. Depending on how it's implemented it could need lookahead or backtrack (to rewind over the unknown token). Or you could flag mandatorily the user part and trigger it on request: (object (standard-stuff) (custom <<<< here trigger the DOM parser I wouldn't really like such kind of a mixed parser however (personal opinion) -- Lorenzo Marcantonio Logos Srl _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
