From: stephan b. <st...@ei...> - 2003-09-09 04:03:36
|
On Sunday 07 September 2003 20:17, stephan beal wrote: > trees) and is in the SerNodeSerializer interface. i don't yet have > the xml reader working, but it shouldn't be terribly difficult to do. > i haven't yet settled on an interface for wrapping these parsers > within the SerNodeSerializer interface. The fact that it's lex will > be as deeply hidden as possible, of course. i have the XML-based reader/writer working, but it only works for the rather limited XML structure we've been using all this time: <node class="Foo"> <property>foo</property> ... </node> The whole parser is made up of only 4 rules, totaling approximately 50 lines. Of course it doesn't do anything interesting like converting &tokens;. i've factored out the dom-building side into a separate class and hidden the lex parsers behind a quasi-api, so i finally have both the txt and xml parsers working together in the same app (this was more work than it should have been, as a side-effect of how one subclasses FlexLexer). -- ----- stephan st...@ei... - http://www.einsurance.de "...control is a degree of inhibition, and a system which is perfectly inhibited is completely frozen." -- Alan W. Watts |