Deserialization of numerics should follow general rounding rules

[Francois Normandin]

I’ve noticed that “from JSON text” ignores the decimal characters when deserializing to an integer.

‌

Using the “Fract/Exp String to Number” instead of “Scan from String“ would fix the issue. (Use System Decimal Point = False)

‌

[James Powell]

That does make sense. Need to check for any performance cost of switching the function.

[James Powell]

Complication here is that arrays of integers are converted by the inbuilt JSON primitive (for speed reasons). Need to make sure that arrays and scalar integer conversion are consistent with each other (see also #93).

[James Powell]

Performance tests in LV2020 suggest this change is faster; fast enough to solve #93 and displace the problematic use of teh inbuilt JSON primitive for arrays.

[James Powell]

Inbuilt JSON primitive also converts 0.99 to integer 0, so does need replacing.

[James Powell]

Resolved for arrays also