parseInt Question

jezjones29 · **Posted:** August 28th, 2013, 3:02 pm

Does anyone know why opus can handle..
parseInt('FFFF',16) = 65535
but not
parseInt('FFFFF',16) = 1.04858e+006

mackavi · **Posted:** August 28th, 2013, 5:43 pm

um - it's not it's returning 1048575 when I test it :-?

Perhaps it's the context?

Mack

jezjones29 · **Posted:** August 29th, 2013, 10:05 am

Very strange. I wonder if it's memory related. Is it the same with 9xF:
parseInt('FFFFFFFFF',16) I get 6.871947674e+010
In JavaScript I can get to 18 before it does that:
http://jsfiddle.net/hq8d9/1/

mackavi · **Posted:** August 29th, 2013, 1:31 pm

Yes, I too get scientific notion at that point.

Are you really running 8.06?

Mack

jezjones29 · **Posted:** August 29th, 2013, 3:10 pm

ok, thanks for testing.

I've updated my profile too.

Lar_123 · **Posted:** August 31st, 2013, 11:40 pm

jezjones29 wrote:

Does anyone know why opus can handle..
parseInt('FFFF',16) = 65535
but not
parseInt('FFFFF',16) = 1.04858e+006

I guess good if that issue can be resolved in the opus program.

Meanwhile if you need it, here is a workaround.

Code:

testofParseint = String.format("32.0",parseInt('FFFFFFFFF',16) )
//result is:    68719476735
//use whatever number of digits you think large enough, leading zeroes do not display at least for hex base

Currently, OpusPro v7.06

Digital Workshop

parseInt Question

Who is online