Hi, I created a fork of JSON::XS called JSON::SIMD that uses the simdjson library for decoding, but retains the encode part with few changes.
I also ran into issues with quadmath builds. For the offending line in encode_sv I've used
quadmath_snprintf(enc->cur, enc->end - enc->cur, "%.*Qg", (int)N +V_DIG, SvNVX(sv));
According to my commit message, this fix came from Cpanel::JSON::XS.
As for the test, I've "fixed" it like this:
like($js,qr/\[(?:1.01[Ee]\+0?30|1010000000000000000000000000000)\]/, ' +digit 1.01e+30');
I considered this to be a remote edge case, so I'm not too bothered about it.
About the theoretical matters regarding the JSON format... the most recent document closest to a standard is RFC 8259. As you can see it's not very formal, and it says nothing about prescribed ranges in which numbers must be represented as integers or floating point numbers, nor anything about required precision. The remark about interoperability and IEEE 754 doubles indicates that with quadmath number ranges, we are already in "you get to keep the pieces" territory.
In reply to Re: JSON-XS on quadmath builds of perl
by kikuchiyo
in thread JSON-XS on quadmath builds of perl
by syphilis
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |