(Sorry Bill for the duplicate, I missed the list the first time) On Wed, Oct 3, 2012 at 10:27 AM, Bill Moseley <[email protected]> wrote:
> I also use JSON (or JSON::XS) so not clear if JSON::ANY behaves the same. JSON::Any should behave identically to JSON or JSON::XS ... it is only an API shim. If it doesn't that is a bug in JSON::Any and I would love to have a fix for that. That said, it sounds like the right answer here may be to drop JSON::Any and just use JSON. -Chris
