I hate these. You don’t need to program for very long before you see one of these. And, you get used to the idea that when it says there’s an error on a blank line, that it means something isn’t properly terminated on one of the previous lines. But, man, I hate these.
At the very least, you’d hope that by now compilers/interpreters would be able to say “error somewhere between line 260 and 265”. Or, more usefully “Expected a closing ‘)’ before line 265, opening ‘(’ was on line 260”.
Error on <blank line> just pisses me off because the compiler / interpreter should know that that isn’t true. Whoever wrote the compiler is a seasoned developer who has been hit by this kind of error message countless times. They must know how annoying it is, and yet…
My personal favorite is when it complains about a missing semicolon. So it’s 100% knows what the problem is, it knows where the problem is, and it knows how to fix it. But it’s not going to fix it out of spite.
Oh boy, are you gonna LOVE Javascript
Is your point that JS doesn’t really need semicolons at all any more?
Not just that, it’s the reason why it doesn’t need semicolons: https://en.wikibooks.org/wiki/JavaScript/Automatic_semicolon_insertion
Javascript and html are more suggestions on how to write something that may work in a web browser.
im_in_danger.exe
