('binary' encoding is not supported, stored as-is) In-Reply-To: <031901c31b3a$f633d130$0100a8c0at_private> That makes more sense. From the JS 2.0 spec at mozilla.org (http://www.mozilla.org/js/language/js20-1999-03-25/types.html): integer: Double-precision IEEE floating-point numbers that are mathematical integers, including positive and negative zeroes but excluding infinities and NaN number: Double-precision IEEE floating-point numbers, including positive and negative zeroes and infinities and NaN So what your seeing is loss of precision in the mantissa, I guess? Funny that they would choose to call floating point without NaN and +-Inf an "integer". The intervals look funny. Are they consistent with this description? Cheers, ~x > >I'm not a Javascript expert, but I think the issue isn't one of >overflow, it's that the engine doesn't really store those ints with 64 > <snip> >Produces the following: >-------------------------------------------------- >Starting with 2^56 (72057594037927940) >72057594037927940 != 72057594037927950 >72057594037927950 != 72057594037927970 >72057594037927970 != 72057594037927980 >72057594037927980 != 72057594037928000 >72057594037928000 != 72057594037928010 >
This archive was generated by hypermail 2b30 : Fri May 16 2003 - 15:56:32 PDT