News for hackers. Stuff that matters.
Re:JSHint: An Community Driven Fork of JSLint by jacobbijani on Friday February 18, 2011 @02:44PM (#2236923)
Is there any reference for the reasoning behind error-ing on the standard for loop?
Re:JSHint: An Community Driven Fork of JSLint by callahad on Friday February 18, 2011 @03:12PM (#2237032)
It's concerned about the declaration of i within the loop's first term. Since JavaScript only has function-level scope, that variable leaks into the broader context, which can lead to unexpected behavior.
Re:JSHint: An Community Driven Fork of JSLint by marijn on Friday February 18, 2011 @03:52PM (#2237213)
Not if you actually, you know, know what you're doing. This dumbing down of programming does not work--if you have clueless people working on code, it'll end up broken, no matter how many tool-enforced 'best practices' they follow.
Re:JSHint: An Community Driven Fork of JSLint by evgen on Friday February 18, 2011 @11:05PM (#2238336)
Why would the zen master of JavaScript of which you speak have any need for JSLint in the first place? Us mere mortals are sometimes forgetful and need reminders...
Re:JSHint: An Community Driven Fork of JSLint by Skalman on Friday February 18, 2011 @04:31PM (#2237355)
I can't see why people not liking the defaults (which are great for beginners) can't change their settings.
Re:JSHint: An Community Driven Fork of JSLint by daleharvey on Friday February 18, 2011 @02:53PM (#2236956)

    Problem at line 1 character 6: Move 'var' declarations to the top of the function.
I do prefer having all my vars at the top of the function, loop vars are an exception though.
Re:JSHint: An Community Driven Fork of JSLint by isak2 on Friday February 18, 2011 @03:28PM (#2237106)
I think Crockford is right about that error.

Declaration of variables in the loop could lead to this type of error:

http://cam.ly/blog/2011/01/javascript-interview-question/

(All of the 4 <li> will do alert('4') when clicked, when the programmer expects alert('1'), alert('2'), etc.)

If the variable had been declared at the top, that error probably would not happen.

Re:JSHint: An Community Driven Fork of JSLint by daleharvey on Friday February 18, 2011 @03:37PM (#2237144)
That error would have happened despite if the var was declared at the top or in the loop

    addEventListener("stuff", function() {
        return function(index) {
            alert(index);
        }
    }(i);
is the fix, either way
Re:JSHint: An Community Driven Fork of JSLint by isak2 on Friday February 18, 2011 @04:01PM (#2237247)
Yeah. I meant that the mistake is less likely to have been made in the first place.