fix Int check on large unsigned integers #9
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Large unsigned integers can't always be converted to floats without
losing precision. Checking the NOKp flag and then the NV flag will end
up checking against an inaccurate value and won't register as an
integer.
The
p
flags should not be used for type checking, as they representthat any value exists in the related slot. Their value may not be
accurate.
POK is still checked first, as values like '0e0' will set the IOK flag
if used as a number.