Re:Programming Paradigms for Dummies: What Every Programmer ...
by jstimpfle on Monday November 05, 2018 @08:59AM
(#18382323)
I think this is a hair-splitting distinction and it does not work reliably. Sorry. Things that truly "cannot" happen => you do not know how to recover => you terminate the program. That's it.
[ Parent
| on HN ]
Re:Programming Paradigms for Dummies: What Every Programmer ...
by gwright on Monday November 05, 2018 @09:21AM
(#18382463)
That is why the definition is recursive. If every failure triggers a new exception all the way up the call stack, then your program fails.
Re:Programming Paradigms for Dummies: What Every Programmer ...
by jstimpfle on Monday November 05, 2018 @09:24AM
(#18382478)
Yeah, so what was the point to begin with?
Re:Programming Paradigms for Dummies: What Every Programmer ...
by gwright on Monday November 05, 2018 @09:32AM
(#18382537)
Do you understand Design By Contract? That is the theory that provides the distinction between a function/method finishing with success or with failure. The notion of contract is what distinguishes an exception from a glorified GOTO.
Re:Programming Paradigms for Dummies: What Every Programmer ...
by gwright on Monday November 05, 2018 @07:07PM
(#18387156)
In re-reading, my response comes across as much more flippant than I intended. I was just trying to re-emphasize that the definition of an exception is an integral component of Meyer's design by contract methodology and not a stand alone concept.