What I originally suggested was not a parser, but a set of APIs to
manipulate XML. The parser part (i.e. the piece of code that generates
a parse tree from an XML file) is the simples part of it all. What
is much more tricky is to get the right internal structure to make
operation on the tree efficient and convenient.
That said, I would *not* recommend to rewrite any such thing. It is
a *lot* of work, and as such quite unrelated to boost's goals.
What I had (and still have) in mind is a C++ interface to an existing
implementation (libxml2 actually).
Also I'm not convinced that the main goal should be to conform with
the DOM specs as provided by w3c. Lots of implementers / users consider
its design broken. Instead I'd suggest to try to come up with a 'good'
C++ API, and then build a wrapper around it that provides the legacy
mapping as needed.
Kind regards,
Stefan
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
