Question

103

Why were the new JSLint errors use spaces, not tabs and unsafe character introduced?

rated 0 times [ 105] [ 2] / answers: 1 / hits: 34901 / 12 Years ago, mon, december 17, 2012, 12:00:00

I have been validating my JavaScript using JSLint for about 2 years now and once in a while there are rules that change. In general when JSLint introduces a new rule, there is a checkbox to ignore this rule when parsing, or if you choose to not ignore it then to make your code compliant to it.

As I was running my JSLint validation today, however, I run into these two new errors:

Use spaces, not tabs.

This is not the "mixing of tabs and spaces" error. I am using only tabs. This is a recently modified version of "mixing of tabs and spaces" which now disallows tabs in general.

And:

Unsafe character.

*/

Unsafe character.

_const: {

There are no new options to ignore. I cannot understand what is unsafe about closing a block comment, why it considers _const: { as unsafe when I have nomen: true, (dangling _ in identifiers) or why should I be suddenly switching from spaces to tabs, when I still have the configuration about indentation of 4 spaces being a tab.

Does anyone have an idea why those were introduced to at least how to make JSLint ignore these new rules?

Update:
The Messy White Space option works around the issue but it would cause other unexpected behavior:

if (condition) { 

  //            ^-- there is a space but it won't indicate an error

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

jamila

Add To Favorites

Follow

Total Points: 490

Total Questions: 94

Total Answers: 94

Location: Lebanon

Member since Sun, Aug 2, 2020

4 Years ago

answered 12 Years ago blaisep · Accepted Answer

Well it looks like Douglas Crockford just made a whole lot more people switch to JSHint. Have a look at this commit.

The Mixed spaces and tabs error has been removed, and a new Use spaces, not tabs error has been added in its place. Aside from that, there's one tiny change in that diff that shows the cause of this. The following line (comment added):

at = source_row.search(/ t/);

//                      ^ Space

has been replaced with this:

at = source_row.search(/t/);

//                      ^ No space!

Following that search there's an if statement. If the condition evaluates to true, the Use spaces, not tabs warning is issued. Here's that statement:

if (at >= 0) {

    warn_at('use_spaces', line, at + 1);

}

I hope that this is just a little oversight by Crockford. As you can see, JSLint is now going to raise this warning if you use a tab character anywhere. Unfortuately, his commit messages are completely useless, and the documentation doesn't appear to have been updated, so I can't do anything other than speculate as to the reasons behind this change.

I suggest you abandon JSLint and switch to JSHint right now.