On 5/30/2016 8:28 PM, Nikita Popov wrote: > This proposal adds a new json.precision setting. Why? I've been told that > this is more flexible, which is fair enough, but imho we should have very > strong reasons for introducing new ini settings. Reasons that go beyond "it > might be useful to someone ... maybe?" So what's the particular use-case > here? Where is it necessary to export inaccurate floating point numbers in > JSON? And should such a use-case indeed exist, why is this a global setting > rather than an option of json_encode? Furthermore, note that even without > this new ini option, you always have the option of temporarily changing > serialize_precision for a json_encode call, if you *really* need it. >
I second this remark especially because in my book JSON is just another form of serialization, hence, it should use the same setting. Additionally, how is it possible that global ini settings -- which in my opinion is a sensitive area -- can go through with a 50%+1 vote? -- Richard "Fleshgrinder" Fussenegger
signature.asc
Description: OpenPGP digital signature
