Javascript Lint claims extra semicolon is bad (after `if`)

Question

I have Javascript Lint set up to carry out syntax checking in vim, and when I have a statement such as

if (i > 0){
 i--;
};

It generates the following warning

test.js|160 warning| empty statement or extra semicolon

I thought that it is best to always end statements with semicolons (see here). It's not issuing an error, but why the warning? How can I change this. I don't countless warnings when I am looking for legitimate warnings.

The warning is legitimate. I do think that you should be able to turn it off, if you like, though I can't help you with that, but it's correct. — Michael Krelin - hacker, Oct 28 '11 at 10:25
why though, isn't it better, or at least no worse, to have semi colons after if statements? — puk, Oct 28 '11 at 10:26
I think it's a matter of taste. I do think it's worse, but, as I said, you're entitled to your opinion and technical means to enforce it locally. — Michael Krelin - hacker, Oct 28 '11 at 10:29

score 9 · Accepted Answer · edited May 23 '17 at 12:01

9

Guess it's complaining about the final semicolon after your closing brace.

};

In any programming language I have used, it is not normal to close blocks with semicolons. The block is closed by the closing brace.

There's more discussion on JavaScript: When should I use a semicolon after curly braces?.

edited May 23 '17 at 12:01

Community

1
1

answered Oct 28 '11 at 10:23

ewan.chalmers

16,145
43
60

1

Yes, but my question is why that is a warning. It should be perfectly legal. – puk Oct 28 '11 at 10:26
3

The reason it's a warning is {...} is a complete statement. {...} followed by a semi-colon is two complete statements, one of which is empty. – mah Oct 28 '11 at 10:42
3

Yes, empty statement is perfectly legal. Hence warning, not error ;-) – Michael Krelin - hacker Oct 28 '11 at 10:44

Javascript Lint claims extra semicolon is bad (after `if`)

1 Answers1