To true. Honestly the only type of error you should be scratching your head for 2 hours on is probably logic errors. Although I know just how hard it can be when the error is confusing has hell and you just keep staring at your code until you finally see that stupid error that's been staring you in the face for 2 hours!.... I'm not bitter
Ohhh, okay now I see. Yeah something like that would never be an issue in probably 95%+ languages, and for those that do, any half decent IDE would pick it up.
That "space" must be a chatacter that looks like a space but is actually not considered whitespace by the JavaScript compiler. I expect it is a special Unicode character or something.
Effective solution i like using is having the system print numbers from 1 upwards after each key function. When something freezes or doesn't work , you can check where the printing reached to narrow down the problem section. Of course, this is all assuming the code can compile with errors
Eh, I've hardly gone further than 10 of these, so can easily find them. Burning one bridge at a time....
Its such a lifesaver when working with conditionals too
Its such a lifesaver when working with conditionals too
Going to go back to doing that now actually.