Re:The Grand C++ Error Explosion Competition
by Ididntdothis on Sunday August 18, 2019 @11:51AM
(#20730917)
When I did more C++ i found it weirdly satisfying to get a few hundred or thousands of errors during build and then fixing all of them with only a few changes.
[ Parent
| on HN ]
Re:The Grand C++ Error Explosion Competition
by noncoml on Sunday August 18, 2019 @02:29PM
(#20731938)
When I was in college people would come to me to help them with their C++ compilation errors. My secret? Most of them would start trying to fix the reported errors bottom up. I would start top down and be done with probably one missing semicolon or something simple as that.
Re:The Grand C++ Error Explosion Competition
by Ididntdothis on Sunday August 18, 2019 @03:40PM
(#20732342)
Going top down seems to be the secret. I do mainly C# now but even there a lot of people get confused by looking at the last error on the screen. I always only look at the first error and deal with that before looking at anything else.
Re:The Grand C++ Error Explosion Competition
by mikelward on Sunday August 18, 2019 @03:50PM
(#20732398)
I wish tools defaulted to only showing the first error.
Re:The Grand C++ Error Explosion Competition
by cmroanirgo on Monday August 19, 2019 @04:48AM
(#20736046)
In my experience, having a list to work through is much faster to remedy than fixing one bug at a time, and then recompiling for the next bug. VB drove me nuts for this simple reason.
Re:The Grand C++ Error Explosion Competition
by Ididntdothis on Monday August 19, 2019 @01:07PM
(#20739544)
Agreed. Maybe errors should get displayed in reverse order so you can work your way up through the console window.
Re:The Grand C++ Error Explosion Competition
by persistent on Sunday August 18, 2019 @02:59PM
(#20732125)
If you have thousands of errors it is likely you simply misplaced a comma or semicolon. If you have just one error you are in deep trouble.