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 ]

perigrin (3495)

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 was 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.

Journal of perigrin (3495)

Wednesday February 13, 2008
07:40 PM

JSON::Any 1.16 or Why I Should Be in

[ #35650 ]

So first I saw this when I woke up this morning and checked my feeds. I muttered to myself that I’d need to patch JSON::Any soon and then a coworker pointed out this. All of which is to say:

JSON::Any 1.16 is heading to the CPAN mirrors as we speak. It includes Simon Wistow’s patch for supporting both versions of JSON::Any, as well as some minor documentation clean up and a tweak to the Makefile.PL logic so that you really have to work at it to install JSON::Any without a JSON package.

Hopefully this will make everything better.

(*) Apparently there was a rant/discussion about this on this morning which lead to Simon Wistow’s patch and Acme’s Release … all of which I sadly missed until after the fact.

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.