Comments on: Number.toString bug

By: Annely

Annely — Fri, 20 Nov 2009 13:50:58 +0000

Same Problem in Flex 2.0
I get per Http-XML som strings. One of them is a numberstring: 712041237133483101. I can see them in xml. By displaying that string in a textinput it shows 712041237133483100.
Its only a string. I can’t change the Http-XML, so I have to find a workaround that the string will display as a string and not as a wrong number…
Have anybody a idee?
Thanks!

By: Lucas

Lucas — Tue, 02 Jun 2009 09:08:26 +0000

Same Problem here:
I get a Number from a Webservice: 371640000000009984
Make it to String and get: 371640000000010000
If I look at the Max_Value: 9223372036854775807 everything should be fine.
Other way around: a String: 371640000000009984 to a Number –> everything fine no “rounding” problem.

I look for a workaround (perhaps getting a String from the Webservice instead)….

By: Virgil Cristea

Virgil Cristea — Thu, 20 Nov 2008 12:35:27 +0000

Int cannot store that value I needed. I do not think it is a floating point error as in debug I see the correct value set up in the numberVariable. The problem appears only when I do toString().

By: Keith Peters

Keith Peters — Thu, 20 Nov 2008 12:32:47 +0000

It’s not a bug per se, and the problem is not in the toString method. The problem is that the Number class uses 53 bits to store its values. ints and uints use 32 bits. The number you passed in would take more bits than that to represent. Just try this:

trace(-9223372036854775808);

You get the same result.

53 bits lets you accurately store numbers as large as 9007199254740992. You can store numbers larger than that, but at the expense of accuracy.

By: z

Thu, 20 Nov 2008 11:10:57 +0000

use int?

mabye some floating point error?