Best Practices Exist For A Reason

Re:Best Practices Exist For A Reason by mnutt on Wednesday May 02, 2012 @08:09PM (#3921789)

With separate var statements, you never end up with this situation:

    var foo = 1,
        bar = 2
        baz = 3

In 90% of the cases the code will run the same whether or not there is a comma on line 2, but in the other 10% you will get burned in odd ways now that `baz` is a global variable.

[ Parent | on HN ]

Re:Best Practices Exist For A Reason by Isofarro on Thursday May 03, 2012 @04:08AM (#3922866)

JS Lint is your friend in this case. It will log that

* There's a missing semicolon on line 2

* There's a missing semicolon on line 3

* baz was being used before it was defined.

That's just in a global context. When it's in a function you get a little more:

* the baz line is indented too far - because it's being interpreted as a new statement.

Sure, you could eyeball your code looking for this. Or just use an automated tool that'd do it for you

[ Parent | on HN ]