Re^2: XML-Twig: more efficient tree processing

IMO, if you want incremental parsing with callbacks because your tree does not fit in the memory, XML::LibXML is much harder to use than XML::Twig.

Comment on Re^2: XML-Twig: more efficient tree processing

Replies are listed 'Best First'.
Re^3: XML-Twig: more efficient tree processing by Anonymous Monk on Aug 09, 2012 at 08:04 UTC
Yup, its quite laborious, pretty much like using raw XML::Parser (or HTML::Parser) Where as in Twig you'd say I only want trees out of '/foo/bar/bar' with LibXML (like XML::Parser) you have to build those trees yourself with XML::LibXML::SAX::Parser -- although, there is no reason a XML::Twig type API couldn't be built on top of XML::LibXML::SAX::Parser, its just extra work, given that Twig already exists :)	[reply]

Replies are listed 'Best First'.

Re^3: XML-Twig: more efficient tree processing
by Anonymous Monk on Aug 09, 2012 at 08:04 UTC

Yup, its quite laborious, pretty much like using raw XML::Parser (or HTML::Parser)

Where as in Twig you'd say I only want trees out of '/foo/bar/bar' with LibXML (like XML::Parser) you have to build those trees yourself with XML::LibXML::SAX::Parser -- although, there is no reason a XML::Twig type API couldn't be built on top of XML::LibXML::SAX::Parser, its just extra work, given that Twig already exists :)

[reply]