Strong typing is a meme. People fall for it because they are inept. If you don't have to worry about memory safety, you don't need type safety, the runtime environment is handling that for you.
And stl is a library. A standard library, but a library nonetheless.
That's Lua. In Javascript you have to to add a semicolon at the end of an expression.
You don't, actually. That's a convention to make code clearer to read.
actually i kind of agree with you there, whats the point of bothering with memory sizes if you're not managing it yourself almost fully (talking to the kernel to almost automatically map your memory to ram / whatever), fug ecmascript has shown me the light
er no, its optional
t. poo writing code full of bugs
THE JAVASCRIPT PARSER REQUIRES THE SEMICOLON IN ORDER TO CORRECTLY PARSE THE LANGUAGE BECAUSE OF THE STRUCTURE
You're fucking retarded. The parser only tries to guess it and in a lot of situations will guess it wrong, you fucking pajeet.
NIGGERS SHOULDN'T BE ALLOWED ACCESS TO COMPUTERS!
flaviocopes.com
Shut up, retard.
Well both nodejs and firefox js interpreters don't care about semicolons - it won't even report an error. Don't know what ECMA standard says about that though.
Right, especially, when you're looking for bugs. I spent a lot of hours looking for bugs caused by this "convention".
You had difficulties because there was or because there wasn't semicolons? The convention is to add the semicolons.
Niggers, this doesn't run:
// define a functionvar fn = function () { //...} // semicolon missing at this line// then execute some code inside a closure(function () { //...})();
This does:
// define a functionvar fn = function () { //...}; // semicolon NOT missing at this line// then execute some code inside a closure(function () { //...})();
stackoverflow.com
Even stackoverflow.com-faggots have figured that out. You should always place it instead of just when it causes trouble because it's implementation dependent when in which situations it will cause trouble.
understands from experience.