Re^2: Benchmarks of XML Parsers

I was going to add XML::Bare to the benchmark until I noticed it was returning garbage (as shown here). I think it expects to be handed decoded XML. That's odd, since you need to parse the XML doc to figure out the encoding that was used. Anyway, to make the benchmark fair, you'd have to include the necessary step of decoding the XML for XML::Bare.

Encoding tests code

Comment on Re^2: Benchmarks of XML Parsers Download Code

Replies are listed 'Best First'.
Re^3: Benchmarks of XML Parsers by almut (Canon) on Apr 28, 2009 at 22:34 UTC
I think it expects to be handed decoded XML. I've personally never used it with anything but ISO-Latin-1 (and haven't encountered any problems so far in this regard). But I think it's true it doesn't properly handle unicode, at least not multibyte encodings like UTF-16. OTOH, I just converted an ISO-Latin-1 XML file to UTF-8 (and changed the `"encoding=..."`, of course — though that simply appears to be ignored), and it seems to "work" at least in that - when I Data::Dumper the created object - the appropriate chars are passed through unmodified (encoded) — which probably is because it doesn't do any decoding at all, and simply treats everything as bytes... (part of the less-features-for-speed concept, I guess)	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: Benchmarks of XML Parsers
by almut (Canon) on Apr 28, 2009 at 22:34 UTC

I think it expects to be handed decoded XML.

I've personally never used it with anything but ISO-Latin-1 (and haven't encountered any problems so far in this regard). But I think it's true it doesn't properly handle unicode, at least not multibyte encodings like UTF-16.

OTOH, I just converted an ISO-Latin-1 XML file to UTF-8 (and changed the "encoding=...", of course — though that simply appears to be ignored), and it seems to "work" at least in that - when I Data::Dumper the created object - the appropriate chars are passed through unmodified (encoded) — which probably is because it doesn't do any decoding at all, and simply treats everything as bytes... (part of the less-features-for-speed concept, I guess)

[reply]
[d/l]