Json-c BIGINT disparity

Anyone here had experience with things like these before?

Basically, when using the “other” json extension for PHP which claims to be a drop-in replacement for the original one due to license issues, you get a disparity between results in that numbers over 64bit cannot be parsed as strings, but rather always produce the max BIGINT, and throw a notice at you.

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.