About boost.variant: boost.variant is not compatible to various other boost libraries, mostly because of conflicts with boost::get. (f.e. graph). Also the sender offers a library which uses a different approach, maybe worth considering. And still I think a pluggable solution would be best, where you can choose from different Implementations of Parsers and Datastructures f.e. regards, Jens Weller -------- Original-Nachricht --------
Datum: Thu, 08 Apr 2010 13:58:07 -0400 Von: Stefan Seefeld <seefeld@sympatico.ca> An: boost@lists.boost.org Betreff: Re: [boost] xml?
On 04/08/2010 01:50 PM, Maarten L. Hekkelman wrote:
Op 08-04-10 19:23, Phil Endecott schreef:
So could your XPath implementation be decoupled? What interface does it use to traverse the XML tree? Could it be used on top of a different XML tree implementation, such as a lazy one that stores the text of the XML document, if it provided a similar interface? I think most of it should work. However, the entire XPath specification is build upon the idea that everything is a node and a node does not have to be an element. That's why I changed my object hierarchy.
For the boost.xml library I'm working on I plan to use something akin to boost.variant as the return type of an xpath query. I don't think that the XPath specification should dictate a type hierarchy on a C++ implementation.
FWIW, Stefan
--
...ich hab' noch einen Koffer in Berlin...
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01