Comments on: Why Use JSLint? http://mike.kaply.com/2007/01/11/why-use-jslint/ Mozilla, money, microformats and more Tue, 15 May 2012 05:27:48 +0000 hourly 1 http://wordpress.org/?v= By: Kwang Yul Seo http://mike.kaply.com/2007/01/11/why-use-jslint/#comment-73 Kwang Yul Seo Thu, 08 Mar 2007 03:04:40 +0000 http://www.kaply.com/weblog/2007/01/11/why-use-jslint/#comment-73 Is there any use case which makes the comparison operator == meaningful? I've always wondered why such an operator exists. Automatic type conversion makes me crazy when debugging. Is there any use case which makes the comparison operator == meaningful? I’ve always wondered why such an operator exists. Automatic type conversion makes me crazy when debugging.

]]> By: Wladimir Palant http://mike.kaply.com/2007/01/11/why-use-jslint/#comment-72 Wladimir Palant Wed, 17 Jan 2007 23:05:17 +0000 http://www.kaply.com/weblog/2007/01/11/why-use-jslint/#comment-72 Correction to the above: I did find a few minor glitches with JSLint. Yet all the noise that it outputs doesn't exactly make it easy... Correction to the above: I did find a few minor glitches with JSLint. Yet all the noise that it outputs doesn’t exactly make it easy…

]]> By: Wladimir Palant http://mike.kaply.com/2007/01/11/why-use-jslint/#comment-71 Wladimir Palant Mon, 15 Jan 2007 10:10:56 +0000 http://www.kaply.com/weblog/2007/01/11/why-use-jslint/#comment-71 Michael, I always run Firefox with javascript.options.strict switched on. It catches undeclared variables and some other common mistakes (like mistyping a property name which causes "reference to undefined property" warnings). I tried JSLint but some parts of the enforced syntax are pretty ridiculous - like mandatory block parentheses and using === instead of ==. Most warning types cannot be disabled which causes lots of noise, so JSLint is pretty useless for me right now. And I really can't see the added value if compared to Gecko's own warnings. Michael, I always run Firefox with javascript.options.strict switched on. It catches undeclared variables and some other common mistakes (like mistyping a property name which causes “reference to undefined property” warnings). I tried JSLint but some parts of the enforced syntax are pretty ridiculous – like mandatory block parentheses and using === instead of ==. Most warning types cannot be disabled which causes lots of noise, so JSLint is pretty useless for me right now. And I really can’t see the added value if compared to Gecko’s own warnings.

]]> By: Jon Williams http://mike.kaply.com/2007/01/11/why-use-jslint/#comment-70 Jon Williams Fri, 12 Jan 2007 00:47:41 +0000 http://www.kaply.com/weblog/2007/01/11/why-use-jslint/#comment-70 <i>using == where I should use ===</i> Hm, I didn't realize javascript had that operator. How does it know when a lazy comparison is bad though? <i>Do you see the problem there? Because I didn’t have “var” in front of toolbar, I was affecting the global variable toolbar</i> I should really look into this because I had <a href="http://wizardishungry.com/blog/archive/when-to-use-google-to-solve-your-problems-and-when-to-solve-things-yourself" rel="nofollow">the same kind of problem</a>, but it only caused negative side effects in msie *and* it was in Prototype's try{} block which discards exceptions. Hooray. I blame my undergraduate CS education for not teaching me about lint ... or version control, or MVC, or relational databases or... using == where I should use ===
Hm, I didn’t realize javascript had that operator. How does it know when a lazy comparison is bad though?

Do you see the problem there? Because I didn’t have “var” in front of toolbar, I was affecting the global variable toolbar

I should really look into this because I had the same kind of problem, but it only caused negative side effects in msie *and* it was in Prototype’s try{} block which discards exceptions. Hooray. I blame my undergraduate CS education for not teaching me about lint … or version control, or MVC, or relational databases or…

]]> By: J http://mike.kaply.com/2007/01/11/why-use-jslint/#comment-69 J Thu, 11 Jan 2007 22:23:20 +0000 http://www.kaply.com/weblog/2007/01/11/why-use-jslint/#comment-69 http://kb.mozillazine.org/Javascript.options.strict will help you as well. :) http://kb.mozillazine.org/Javascript.options.strict will help you as well. :)

]]> By: Gopalarathnam Venkatesan http://mike.kaply.com/2007/01/11/why-use-jslint/#comment-68 Gopalarathnam Venkatesan Thu, 11 Jan 2007 17:40:45 +0000 http://www.kaply.com/weblog/2007/01/11/why-use-jslint/#comment-68 JSLint checks for the coding styles to match with Douglas Crockford's guide [http://javascript.crockford.com/code.html] and hence you should break after an operator ;) Also, I believe it reports a warning when using ++. That said aside, its always better to declare variables (using the var keyword) at the start of the function since JavaScript has function scope, which would emphasize this. I would prefer: function f() { var i, // some more vars // ... for (i = 0; // ...) // ... } instead of: function f() { // ... for (var i = 0; // ...) // ... } JSLint checks for the coding styles to match with Douglas Crockford’s guide [http://javascript.crockford.com/code.html] and hence you should break after an operator ;) Also, I believe it reports a warning when using ++.

That said aside, its always better to declare variables (using the var keyword) at the start of the function since JavaScript has function scope, which would emphasize this.

I would prefer:

function f() {
var i, // some more vars

// …
for (i = 0; // …)
// …
}

instead of:

function f() {
// …
for (var i = 0; // …)
// …
}

]]> By: Doug Turner http://mike.kaply.com/2007/01/11/why-use-jslint/#comment-67 Doug Turner Thu, 11 Jan 2007 16:24:29 +0000 http://www.kaply.com/weblog/2007/01/11/why-use-jslint/#comment-67 Do you know anyone that has tried to run mozilla js code through jslint? Do you know anyone that has tried to run mozilla js code through jslint?

]]>