Corrupt Unwinding on Errors
Eyal Lotem
eyal at weka.io
Tue Jan 22 09:48:47 UTC 2019
On Tuesday, 22 January 2019 at 09:14:30 UTC, Iain Buclaw wrote:
> On Tue, 22 Jan 2019 at 09:15, Eyal Lotem via Digitalmars-d
> <digitalmars-d at puremagic.com> wrote:
>
> Throwing an Error inside a nothrow function is allowed, unlike
> an Exception. As for what happens if that were to ever happen
> is undefined, because you're not supposed to recover from it.
If you're not supposed to recover, then what's the point of
corrupt unwinding of the stack?
It would be much safer to terminate the program right there,
allowing a user-installed handler to do its thing before
termination.
Not unwinding is far better than *corrupt* unwinding.
More information about the Digitalmars-d
mailing list