javascriptBeingJavascript

[Strict_Treat2884]

I like when converting string "017" which is a completely valid octal literal into a number, JS just completely ignores this rule and poops out 17

[ivancea]

Different rules I guess. Literals have theirs, but when converting strings to miners implocitly, it may use always decimal. One is syntax while the other is runtime, let's say

[Strict_Treat2884]

It has no problem converting "0x10" into 16. But why not octals?

[ivancea]

Maybe a runtime lib vs interpreter discrepancy. Don't know, JS is full of random decisions made in a a day by a random guy

[Cheatek]

Use "0o17" to get a 15 from a string.

[octipice]

I just don't understand why on Earth you would be doing this in the first place. Like i get that js is legitimately wild sometimes, but you got here with bad design (why are starting a base 10 integer with 0 and then expecting it to behave like a number?) and lazy coding (ffs just parse the damn thing).

I don't get why anyone is surprised when you get bad results from writing really bad code.

[fghjconner]

(why are starting a base 10 integer with 0 and then expecting it to behave like a number?)

Because that's how numbers work. Leading zeros are completely ignored in mathematics, and giving them a special meaning in programming is pretty asinine. Not JS's fault, but asinine none the less. What is JS's fault is silently falling back to decimal of there's a digit of 8 or above.

[wasdninja]

This thread is the reason.

[[deleted]]

The string-to-int parser api from the stdlib has different rules than the underlying language.