Comments on: More JSLint, less JSWTF

By: Allen

Allen — Tue, 23 Feb 2010 18:35:25 +0000

Nigel: Indeed. The trailing-zero-means-octal is a lot more dangerous when you’re using strings though, since they can be user input like a credit card expiry year. I guess the confusing part is:

“09″ == 9; // true
parseInt(“09″) == 9; // false

Andy: The nice thing about it running on save is that it can pop up if there’s a problem, and be silent if not. Pretty nice.

By: Andy Lumb

Andy Lumb — Tue, 23 Feb 2010 16:44:18 +0000

JSLint / Javascript Lint have saved my ass a bunch of times. I also use them for syntax checking. IE will give you “expected }” on the last line of the file… JSLint will give you a reference to where the problem actually is. I wrote a how-to on getting them running in Notepad++ here: http://stackoverflow.com/questions/1046810/using-jslint-in-notepad/1046826#1046826 . I hooked those scripts up to “F9″ and run that before I even switch to the browser.

By: Nigel

Nigel — Tue, 23 Feb 2010 07:51:19 +0000

Even as a total non-Javascript-programmer I’ve been enjoying it, though the gigantic “I see what you did there” image at the top of every single freakin’ page is starting to get on my nerves a little.

I’m not sure exactly what octal’s deal is, but Javascript is not the only language that has succumbed to its charms. C/C++ do a little better, GCC (at least, probably others, I’m not rebooting into windows to check MSVC) will validate individual digits for you so you can use that EXACT example, but…

printf(“%d\n”, 012); // prints ’10′