Once had a missing semi colon at the end of a c header file. The compiler kept complaining about the c file and never mentioned the header. Not all errors lead you to the right place.
Though most of the time people just don’t read them. The number of problems I have solve for people by just copy pasting the error they gave me back to them…
Ah, but you see, JavaScript is not so straightforward. It tries to help you by automatically inserting missing semicolons, but the approach that it uses is that it will insert them in the first place where doing so would make the code parse. This, unfortunately, means that semicolons are often inserted in places where you were not expecting them, so the advice is to always include them manually yourself so that you are never unpleasantly surprised.
It’s just the “Press Next until installation completes” mentality crossing over to the programming side.
You see a dialogue with a red icon and escape it as fast as possible.
You see red text, you just think it is an error and ignore what it says, expecting it to be useless (or maybe not expecting anything at all}
Then when someone tells you to rad the errors, you read them and don’t find them useful because all those years of using computers, you didn’t learn to understand that stuff, no matter how easy it was.
Do people not read compiler errors or something? Finding missing semicolons is easy.
It’s super fucking annoying in Python when you forget a comma between strings and they get concatenated.
The program usually runs just fine after that too.
You fool, it will tell you the error is on a blank line.
Once had a missing semi colon at the end of a c header file. The compiler kept complaining about the c file and never mentioned the header. Not all errors lead you to the right place.
Though most of the time people just don’t read them. The number of problems I have solve for people by just copy pasting the error they gave me back to them…
Ah, but you see, JavaScript is not so straightforward. It tries to help you by automatically inserting missing semicolons, but the approach that it uses is that it will insert them in the first place where doing so would make the code parse. This, unfortunately, means that semicolons are often inserted in places where you were not expecting them, so the advice is to always include them manually yourself so that you are never unpleasantly surprised.
example:
()=>{ return {k:"v"}; // returns the object } ()=>{ return // returns undefined {k:"v"}; // unreachable }The example will be unpleasantly surprising, no matter where you put semicolons.
It’s just the “Press Next until installation completes” mentality crossing over to the programming side.
You see a dialogue with a red icon and escape it as fast as possible.
You see red text, you just think it is an error and ignore what it says, expecting it to be useless (or maybe not expecting anything at all}
Then when someone tells you to rad the errors, you read them and don’t find them useful because all those years of using computers, you didn’t learn to understand that stuff, no matter how easy it was.