Re: Perl XML::Parser failing tests

From: Robin Berjon <[email protected]>
> On Mar 22, 2010, at 23:39 , Jenda Krynicky wrote:
> > As best I know (I just looked) XML::LibXML::SAX still says:
> > 
> > "NOTE: At the moment XML::LibXML provides only an incomplete 
> > interface to libxml2's native SAX implementation. The current 
> > implementation is not tested in production environment. It may causes 
> > significant memory problems or shows wrong behaviour. If you run into 
> > specific problems using this part of XML::LibXML, let me know."
> 
> I think that that's a documentation bug... It's possible that it might
> not expose everything that libxml2 does but it's stable. At least,
> I've used it in production and haven't seen it keel over. 

Fine. Though this documentation bug (if it was that back then) was 
the last drop that forced me to stop trying to understand the 
gobbledygook of SAX documentation and go with XML::Parser when 
deciding what to base XML::Rules on.


> 
> > So what's actually the golden SAX parser we are supposed to install 
> > to solve all our problems? I looked into XML::SAX and a few more and 
> > did not find any pointers to available SAX parser. Though I have to 
> > admit I did not spend much time looking.
> 
> The point with SAX is that you don't need to have the one golden
> parser. That being said, if you want something reliable and reasonably
> fast (keeping in mind that SAX isn't the fastest option - pull APIs
> will get you better speed) XML::LibXML::SAX and XML::SAX::ExpatXS will
> work just fine. 

You don't need a golden parser, but there should at least be a 
recommended one. Preferable such that doesn't warn you that it's 
incomplete and not tested.

> > SAX itself has a plethora of modules, not based on a SAX parser, but 
> > actually being a SAX parser which confuses the issue. 
> 
> I'm sorry, I'm not sure what you mean here :)

That it's hard to compare the number of modules based on XML::Parser 
and SAX when there are tens of interdependent or competing modules 
implementing SAX.

> My bet is that for the most part people are using XML::LibXML (but not the SAX bits).

Which means they slurp the whole XML into memory. Something I can't 
afford to do most of the time.

If you want to generate a maze of objects out of the XML then LibXML 
is most likely the best solution. Agreed.

Jenda
===== [email protected] === http://Jenda.Krynicky.cz =====
When it comes to wine, women and song, wizards are allowed 
to get drunk and croon as much as they like.
	-- Terry Pratchett in Sourcery

_______________________________________________
Perl-XML mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs