Chasing a missing semicolon for 3 hours, it was actually a curly brace

I was helping my nephew with a JavaScript project last Tuesday and he kept getting this weird error that pointed to line 47. We stared at that line for a solid 3 hours, checking every single semicolon and bracket. Turned out the issue was a stray curly brace on line 12 that closed the function early, so everything after it was just floating in space. My first real coding job back in 2009, I had the same kind of problem with a Python script and it took me two full evenings to figure out. Have you ever spent way too long on something that ended up being a one character fix, or is that just my bad luck? - Ivan

0 comments

0 Comments

No comments yet

Be the first to share your thoughts on this discussion.