parseInt() value help

[Christoph Hart]

Why JavaScript treats a number as octal if it has a leading zero

var x = 010; console.log(x); //8 JS engine convert the number x to octal number. Why it happens? How can I prevent it?

Stack Overflow (stackoverflow.com)

[Dan Korneff]

@Christoph-Hart thanks for this! Math.round gets the job done, so I'm happy :)

[Casey Kolb]

Welp, it's August, so "08" by JUCE time, and this just broke all of my licensing systems lol. Time for an update to Math.round()

[Christoph Hart]

Wow that sounds super annoying.

If you want to globally deactivate octal number parsing, just make that function return always false:

HISE/hi_scripting/scripting/engine/JavascriptEngineParser.cpp at e4b8330a3c6b19b333b3544e9f4f599f3ce9726d · christophhart/HISE

The open source framework for sample based instruments - HISE/hi_scripting/scripting/engine/JavascriptEngineParser.cpp at e4b8330a3c6b19b333b3544e9f4f599f3ce9726d · christophhart/HISE

GitHub (github.com)

[Natan]

@Christoph-Hart Thanks Christoph
Is This Helps To Fix The Frontendmacros Aswell?
Values Looks Strange There Too

[Natan]

Update:
Return False is NOT The Answer :/
And Console, Shows This Error, Even In A Project WIth Nothing Than GUI Size

Line 1, column 28: Syntax error in numeric constant {SW50ZXJmYWNlfHwyN3wxfDI4}

[Casey Kolb]

@Christoph-Hart It's all good. It was a 5 minute fix, but a several hour debug haha. Fortunately, I don't think it broke the compiled plugin.

[civet]

confused

I just used this function to parse date and time. It's OK when using javascript in browser.

for(var i = 0; i < 10; i++)
    console.log(parseInt("0" + i));

// 0 1 2 3 4 5 6 7 8 9

but weird in HISE:

for(i = 0; i < 10; i++)
	Console.print(parseInt("0" + i));

// 0 1 2 3 4 5 6 7 0 0

finally, I do a trick:

for(i = 0; i < 10; i++)
	Console.print(parseInt("+0" + i));

// 0 1 2 3 4 5 6 7 8 9

[Lindon]

@civet HISEScript != javascript

[civet]

@Lindon Yes, I know. I have read the docs carefully.

but parseInt() is very commonly used in scripts. and it's likely parseInt() in HISE does not support the second parameter.

parseInt("010", 10); // always return 8 in HISE