09-16-2010 version has bug
- I've also tested the newcap option on the web version at http://www.JSLint.com/ .
That is also working correctly.
I'm using the Web version one too and yes I've cleared my cache and newcap is even when manually set to false.
Just tested it again and I'm getting the same response
Problem at line 432 character 25: A constructor name should start with an uppercase letter.
and I have
/*jslint white: true, browser: true, devel: true, windows: true, sub: true, undef: true, newcap: false, nomen: true, eqeqeq: true, plusplus: true, bitwise: true, regexp: true, immed: true, strict: true */
as my second comment in my file.
- Thats not a good idea Douglas, I would still like very much to be able to have that one option off as I have to use a 3rd party API that is not strict. and that is the primary area of contetion and I don't want my screen mucked up by in this case erroneous errors.
- You should never label non-strict code as strict. There is a contract that comes with "use strict";.JSLint helps you to honor that contract.
- --- In email@example.com, douglas@... wrote:
>Ok given that constraint what is the best set of options that will get me as close to strict as possible and still permit me to use class constructor names that start with lowercase? I'm wanting to maintain as close to strict as I can, however I have no control over whether we use the 3rd party API at my work. It is required use for the project I'm on.
> You should never label non-strict code as strict. There is a contract that comes with "use strict";.JSLint helps you to honor that contract.
I am most grateful for any assistance, thank you in advance.
> use class constructor names that start with lowercase? I'm wantingYou might be able to create a local alias for the API's constructors:
> to maintain as close to strict as I can, however I have no control
> over whether we use the 3rd party API
var Foo = lib.foo;
var instance = new Foo();