Now, I noticed that some conversions during the parsing process do not have the required precision. For example, a 64-bit integer from the file, such as "73847942565529089", is stored as the QJsonValue "73847942565529088". The integer "73847942566053377" results in "73847942566053376". There are more similar cases, where the last digit is not correct. How can I ensure a correct conversion/parsing for such values?

It seems that the integer limits for IEEE 754 double precision data are the problem here. Is there any way to bypass this problem (to get the "original" string during the parsing, etc.)?

]]>Now, I noticed that some conversions during the parsing process do not have the required precision. For example, a 64-bit integer from the file, such as "73847942565529089", is stored as the QJsonValue "73847942565529088". The integer "73847942566053377" results in "73847942566053376". There are more similar cases, where the last digit is not correct. How can I ensure a correct conversion/parsing for such values?

It seems that the integer limits for IEEE 754 double precision data are the problem here. Is there any way to bypass this problem (to get the "original" string during the parsing, etc.)?

]]>You're right, the issue stems from the original JSON specification which represents all numbers as double-precision floating point numbers (or at least, it was originally interpreted this way). There's currently no way to parse 64-bit integers using QJson, but there's a "recent discussion":http://comments.gmane.org/gmane.comp.lib.qt.devel/20202 among Qt engineers on how to work around this.

In the meantime, you could store your numbers as strings, and then manually convert them to integers.

]]>