Problem about float type about reton

[h3x4n1um]

Thankyou for pointing out, I'm gonna look into this special case

[h3x4n1um]

This problem can be fixed by using std::numeric_limits std::isnan and std::isinf

My problem is when converting json2rton, if it reads a Infinity, -Infinity or NaN, should it processes as string or floating-point type? And if it processes as floating-point what if someone writes in json like this:

{"Infinity": "NaN"}

[nineteendo]

If someone writes "Infinity": "NaN" in json this should definitely be treated as a string, no need to detect that.

Thanks for pointing this out, luckily in python with the json library allow_nan is set to True by default, so this doesn't cause issues in my python alternative to RETON.