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...)
JSON::XS
JSON::Syck
JSON::Any
YAML
YAML::XS
YAML::Syck
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.
Get you started? (Score:1)
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?
Re: (Score:1)
XML::Parser
Yes, all not as bad as the number of 'one true' JSON/YAML parsers atm.
Re: (Score:1)
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.
Re: (Score:1)
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.
Re: (Score:1)
Yes, Windows is an issue. And yes, I hope Strawberry fixes this for good.
Bruce Dickenson Rules! (Score:1)
I got a fever, and the only cure is ..
MORE JSONsorry, it just had to be done