JSLint validation of this snippet

1: function foo() {}
2: 
3: foo(1
4: );
5: 
6: foo(
7: );

gives this error:

Error:

Problem at line 3 character 5: Line breaking error ')'.

foo(1

Is this a JSLint bug?

JSLint validation of this snippet

1: function foo() {}
2: 
3: foo(1
4: );
5: 
6: foo(
7: );

gives this error:

Error:

Problem at line 3 character 5: Line breaking error ')'.

foo(1

Is this a JSLint bug?

• javascript
• jslint

Share Follow edited Feb 18, 2009 at 23:35 Rob Kennedy 163k2323 gold badges285285 silver badges478478 bronze badges asked Feb 18, 2009 at 22:55 alex2k8alex2k8 43.2k6060 gold badges172172 silver badges224224 bronze badges

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 13

It's not a bug. JSLint does more than syntax checking: It enforces certain coding conventions. If you revalidate with the "Tolerate sloppy line breaking" option turned on, you won't get an error.

From the JSLint Documentation:

Line Breaking

As a further defense against the semicolon insertion mechanism, JSLint expects long statements to be broken only after one of these punctuation characters or operators:

, . ; : { } ( [ = < > ? ! + - * / % ~ ^ | & == != <= >= += -= *= /= %= ^= |= &= << >> || && === !== <<= >>= >>> >>>=

JSLint does not expect to see a long statement broken after an identifier, a string, a number, closer, or a suffix operator:

) ] ++ --

JSLint allows you to turn on the Tolerate sloppy line breaking (laxbreak) option.

Semicolon insertion can mask copy/paste errors. If you always break lines after operators, then JSLint can do better at finding them.