Panicking on the error is much better than letting the system work continue on an undefined behaviour (good luck with debugging if you are ignoring all assertions)!
IMO there's a place for both. A print statement will reveal a flaw in the programmer's thinking regarding the control flow of the program and the state at that time. If a print statement gives something unexpected, you know exactly where to look in the debugger. If it gives you what you expected, it reveals the problem may be elsewhere
7 Comments
HiddenLayer5@lemmy.ml · 9 pts · 3y
Just ship it with debug flags so your program always generates a stack trace to the user!
raubarno@lemmy.ml · 6 pts · 3y
Panicking on the error is much better than letting the system work continue on an undefined behaviour (good luck with debugging if you are ignoring all assertions)!
elouboub@kbin.social · 4 pts · 3y
Makes me think of devs who debug with print statements instead of a debugger and breakpoints.
lens_r@kbin.social · 8 pts · 3y
IMO there's a place for both. A print statement will reveal a flaw in the programmer's thinking regarding the control flow of the program and the state at that time. If a print statement gives something unexpected, you know exactly where to look in the debugger. If it gives you what you expected, it reveals the problem may be elsewhere
Fabiozeh@lemmy.world · 7 pts · 3y
Well, Kernighan himself said "The most effective debugging tool is still careful thought, coupled with judiciously placed print statements."
If it was good enough for him...
erbs@lemmy.ml · 5 pts · 3y
/me glances sideways at codebase
taylus@lemmy.ml · 3 pts · 3y
would it help if I returned -2147483648?
duskfall@lemmy.world · 1 pts · 1y