Hi, thanks for looking into this. I just had a look at the code involved and I believe I just fixed it: https://github.com/espruino/Espruino/commit/3c700f9d92e73d08dc28a60abd29915a8abd9499
If you try with the latest builds hopefully you'll have some luck.
Floating point is a bit of a nightmare as any error could be:
If this comes up in future one solution might be to compare (new Float64Array([1234.50])).buffer which gives you the dependable, non-fuzzy binary representation of the underlying floating point number.
© Espruino, powered by microcosm.
Report a problem