Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

XML::Tiny 13 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • That this isn't an XML parser. It is majorly broken in various ways. It's more of a tag-soup parser. I still think you should change the name of it.
    • You're right. It should be called "XML::Retarded", and come with a special helmet that its users should have to wear for if/when they walk into a door and go bonk and cry.

      And what's this guy going on about the other modules having too many dependencies? XML::Parser::Lite has none, last I looked. And wasn't RETARDED.

      • Unless I'm missing something, XML::Parser::Lite is not a standalone module, it only comes embedded inside SOAP::Lite, which has 60 bugs, 16 cpan testers failures, and has a dependency on XML::Parser.

        Unless you are talking about something else.

        Additionally, ::Tiny modules always are a bit controvertial. There's always arguments about where to draw the line between feature-set and code size.

        How EXACTLY is it retarded?
        • 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.

          • "His unescaping logic is daffy" is not constructive criticism. Please try again.

            "His attribute syntax rejects half the XML that I write in the course of a day" is not constructive criticism. Please try again.

            That is, please try again if you expect me to pay any attention.

            • The spec is right there. It's easy to read. It's even pretty easy to write a valid parser for it (I wrote XML::SAX::PurePerl in a couple of days, although it is admittedly lacking in a few areas, but it tries). There's even a bunch of fairly good test suites out there for XML. Try James Clark's stuff for a starter. Or fire the stuff in XML::SAX::PurePerl at it. People don't have time to list all the XML parsing bugs out for you when it purposely avoids being an XML parser. But if you're going to call it an
              • I was careful to list the ways in which it is not compliant with the spec. If despite that people expect it to comply with the spec then they really are far too stupid for me to care about.

                I would note that despite the doom-saying XML fanboys in this thread, I have had more feedback from people saying "thanks for this really useful module" than I have for any other module I have released. Funny, that. Y'know, I think that because I'm such a nice person, I'll continue in my evil ways and keep releasing

                • I was careful to list the ways in which it is not compliant with the spec.

                  Your module's key point of differentiation seems to be that it does not, in fact, comply with the XML spec. Why then are you surprised that people don't think it belongs in CPAN's 'XML' namespace?

                  I'm not sure that referring to people as "XML Fanboys" is helpful either.

                  • On the contrary, its key point of differentiation is that it implements a significant chunk of the XML spec - enough of the spec to be very useful - while imposing minimal burdens on the user.

                    There's an awful lot of things in life and on the CPAN which, like this module, are sufficiently complete to be useful without being perfect. Paracetamol is one example. It is sold as a pain reliever, despite the fact that under some circumstances it will rot the liver, which I am sure is not a particularly pleasan

          • Re: (Score:2, Informative)

            by hex (3272)
            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

            Yes. I've just packaged it up and uploaded it to CPAN, and I'm currently waiting to hear back from the authors about getting co-maint permissions.

            • Okay, I don't know what the permissions on PAUSE are for then, because here it is [cpan.org]. Enjoy!
              • The permissions on PAUSE are for it to be included in the index, so when you say "install XML::Parser::Lite" it actually installs your package.

                Currently it would still install SOAP::Lite
          • > 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,

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.