What was the dumbest error in one of your codes, you have not found for hours?

Answer 1

always the same: typo or missing brackets/semicolon
the code often runs fine though and the error points to the wrong line. typos are hard to find after hours of coding. it looks just right.

Answer 2

Forgetting that " thingy darn it took another " that took another " and created a massive error

Answer 3

Ohhh, yesterday I was sending 4 parameters to a function taking 3...causing a memory violation. Thinking it was a wrong-sized buffer I debugged that (no effect) until I took a headcount...huh. Debug says? Parameter 1's crashing. I'd been modifying 2...delete 1...it works fine. *facepalm*

Answer 4

Missing a semicolon in a cout command. I had to check back to the first lesson to get it right.

Answer 5

Well quite recently: When I was writing extensions on UIColor and UIImage in Swift, I accidentaly placed convenience init which should have been in UIColor into UIImage extension. And the XCode, kept compiling. 15 minutes, half an hour, 45 minutes and did not say anything. I spent over 4 hours on that.

Answer 6

end line statements!

Answer 7

yesterday i put <div style:"background-color:blue" >
ibstead of <div style="background-color:blue"> and i was legit on the verge of tears because my program thingy wasn't working even though i was a million percent sure there was no error. Vut after looking, rereading my notes and mimicking the layout again, I realized that it was suppose to be a = and not a : ... i was frustrated by then.

Answer 8

forgot to add a + sign in an operator, searched for hours

Answer 9

once i wanted to voerwrite the paint Graphics method and I forgot one character. I have searched the error for hours because the codes syntax was right