Numbers are the main thing I assumed you were talking about: the JSON spec is clear though, numbers can be arbitrarily long. The problem is not with the JSON s

Numbers are the main thing I assumed you were talking about: the JSON spec is clear though, numbers can be arbitrarily long. The problem is not with the JSON spec, the problem is when you are converting from one data model to another. Any program which claims to perfectly round-trip the JSON data-model should support arbitrarily long numbers, there's no ambiguity in the spec about that. If you are only parsing JSON as a means to encode your own data-model, then there's no obligation to support arbitrary precision, but users should not expect to be able to round-trip arbitrary JSON data. AFAICT, `--jp` doesn't do anything which would affect the length of supported numbers, even though it's generating JSON.