Slash Boxes
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

use Perl Log In

Log In

[ Create a new account ]

jk2addict (4946)

  (email not shown publicly)
AOL IM: chrislaco (Add Buddy, Send Message)
Yahoo! ID: (Add User, Send Message)

Journal of jk2addict (4946)

Friday December 21, 2007
09:46 AM


[ #35181 ]

I truly believe that the amount of modules on CPAN is an asset to Perl %99.9999 of the time. Why not %100? Here's a list for starters:

JSON 1.x
JSON 2.x (using...)

THose are just the big ones, not even counting JSON::PC and JSON::DWIW, etc.

Clearly, we need an YAML::Any.

And don't get me started on XML.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • XML? What’s there to say about XML? For stream processing of ginormous documents you use XML::Twig, all else is the domain of XML::LibXML. There isn’t anything else. Is there anything else?

    • XML::Simple

      Yes, all not as bad as the number of 'one true' JSON/YAML parsers atm.
      • I won’t go near either of those. XML::Simple is a neat idea on paper that kinda sorta works as long as documents are utterly trivial but scales terribly, so I won’t touch with a 10′ pole. XML::Parser does nothing that XML::LibXML doesn’t do better, but lacks XPath support.

        It is as I said: there’s XML::Twig for 1 in 100 cases, and XML::LibXML for everything else.

        • Being a long time win32 user back in the AxKit days, I have a stupendous hate-hate-kill relationship with LibXML. Getting that and mod_perl and Apache to play nicely was a painful experience.

          LibXML on win32 is a lot better than it used to be, and with any luck, it's inclusion into Strawberry Perl 5.10 will make that pain fade. :-)
  • I got a fever, and the only cure is ..


    sorry, it just had to be done