All the Perl that's Practical to Extract and Report
use Perl Log In
perigrin (3495)
chrisNO@SPAMprather.org
http://chris.prather.org/
AOL IM: marceusx (Add Buddy, Send Message)
After Middle School Chris bounced through various high schools around the state of Florida for a bit. He ended up getting a BA (in English) from the University of Central Florida at about the time others his age were getting their MAs. His (now) wife, their child, and he went to Europe for a bit (there was a programming job in Scotland) and came back unemployed where upon he got offered a job in St. Paul. He moved on from that job after a few years to one where he is paid to do the things he previously did as a hobby. That sounds much more exciting than it really was. Really his life is based on two kids, two cats, and a bunny.
JSON::Any 1.14 (Coping with JSON/JSON::XS 2.0)
So as Ovid recently mentioned JSON (and JSON::XS) recently update themselves to support a common API. While admirable that JSON.pm will now use JSON::XS behind the scenes when possible … they both broke backwards compatability without warning or notice*.
This post however is not to bitch about spilt milk, it is to annouce that JSON::Any 1.14 is winging its way to CPAN and has 100% backwards compat with the old JSON::Any interfaces and so should “just work”. Note that currently 1.14 only supports 2.0+ of JSON/JSON::XS … if this turns out to be not enough I’ll add in the logic to detect which version of JSON is installed and do the right thing but I wanted to get something out there now.
(*) Now I did get an email after the fact stating that this was gonna happen. But this was two days after I got the first failure from cpantesters.
--Larry Wall in str.c from the perl source code
JSON::Any 1.14 (Coping with JSON/JSON::XS 2.0) 0 Comments More | Login | Reply /