All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

His unescaping logic is daffy, and his attribute syntax rejects half the XML that I write in the course of a day. But then, he could always say "I meant to do that!".

He (or you!) should just grab XML::Parser::Lite and release it as a standalone module. The fact that XML::Parser::Lite is currently available only in that SOAP dist is a great big mistake-- and a mistake which bears fixing, which
is more than I can say for this XML::Tiny mess.

> The fact that XML::Parser::Lite is currently available only in that SOAP dist is a great big mistake-- and a mistake which bears fixing

This is primarily because I believe there was (and still is) a valid reason for it NOT to be released as a standalone module: it doesn't handle char/entity references (among other things). While I appreciate Earle Martin's effort to make the module more easily available to people, I think this is a too serious limitation to ignore. SOAP::Lite is able to deal with it, but any other app will need to come up with its own solution.

I'm sure there are ways to fix this; I even wrote another module that doesn't have that limitation (XML::ReParser), but never released to CPAN. This limitation is primarily caused by inconsistencies in how regexps are supported inside ?{} code; you can find more details and references to XML::ReParser here: http://beta.nntp.perl.org/group/perl.perl5.porters/2001/07/msg41148.html [perl.org]

I probably should just use whatever way works to process entities and release both Parser::Lite and ReParser. Paul.