jslint_com at Yahoo! Groups

Moving to Google Plus

douglascrockford — Fri, 05 Apr 2013 17:22:11 GMT

Yahoo Groups has aged really badly, and recently I was locked out of this group a number of times because of Yahoo's operational problems. So I am moving the

Re: option.closure

Jos van den Oever — Thu, 28 Mar 2013 13:12:26 GMT

... The parentheses are required to limit the scope of the type cast. The use of @type for casting is not documented on that page, but there is information on

Re: option.closure

douglascrockford — Thu, 28 Mar 2013 12:42:54 GMT

... Thanks. Please try it now. https://developers.google.com/closure/compiler/docs/js-for-compiler does not indicate that the parens are required. Why are they

Re: option.closure

Jos van den Oever — Thu, 28 Mar 2013 09:34:22 GMT

... I have tried on jslint.com with this fragment: === /*jslint closure: true, white: true */ function cast(arg) { "use strict"; return

Re: get & set

rodobrist — Wed, 27 Mar 2013 23:54:43 GMT

... I use get and set sometimes, I am aware that they are: 1. Not overly performant (js perf type diagnostics). 2. Not compatible in IE < 9 browsers. But in

Re: get & set

Felix E. Klee — Wed, 27 Mar 2013 23:47:39 GMT

On Wed, Mar 27, 2013 at 11:27 PM, douglascrockford ... The idea is that JSLint would warn when it sees something as the following? o.getX = function () {

get & set

douglascrockford — Wed, 27 Mar 2013 23:27:37 GMT

I have been asked to have JSLint always warn on use of get and set. How would you feel about that?

option.closure

douglascrockford — Wed, 27 Mar 2013 21:20:37 GMT

I am experimenting with a new option that will tolerate Google Closure declarations. Please let me know if you see problems or omissions.

Re: combining Closure Compiler type casting with JSLint

Jos van den Oever — Wed, 27 Mar 2013 07:18:35 GMT

... Writing var a = /**@type{!number}*/(b); also has effect on the white-space. JSLint expects the 'b' to be much closer to the '='. This is a check that can

Re: combining Closure Compiler type casting with JSLint

douglascrockford — Tue, 26 Mar 2013 22:23:44 GMT

... I may add option.closure. Is there any more weirdness?

combining Closure Compiler type casting with JSLint

Jos van den Oever — Tue, 26 Mar 2013 20:33:49 GMT

In WebODF, we've been happily using JSLint for some time. It is a terrific tool for non-trivial JavaScript project. In addition to JSLint we are using Closure

Re: JSLint and HTML

hemanrobinson — Mon, 25 Mar 2013 18:13:46 GMT

Thanks for all the advice. We have found a workaround. I am sorry to lose the HTML parsing; it was a useful feature.

Re: JSLint and HTML

Andrew Todd — Fri, 22 Mar 2013 17:09:39 GMT

... You will be better off moving to a build and templating system that pulls in your JavaScript source files and your HTML templates, checks them separately,

Re: JSLint and HTML

falk.werner@... — Fri, 22 Mar 2013 06:14:45 GMT

... Is it good practice to only check parts of a product and not the assembled product ("a single output file") itself?

Re: JSLint and HTML

Felix E. Klee — Thu, 21 Mar 2013 16:47:39 GMT

On Thu, Mar 21, 2013 at 3:37 PM, hemanrobinson ... Good practice is to use separate files during development, and then