The extent of trust in errors and error handling

Chris Wright via Digitalmars-d digitalmars-d at puremagic.com
Mon Feb 6 09:25:01 PST 2017


On Mon, 06 Feb 2017 09:09:31 +0000, Dominikus Dittes Scherkl wrote:

> On Monday, 6 February 2017 at 06:08:22 UTC, Chris Wright wrote:
>> On Sat, 04 Feb 2017 23:48:48 -0800, Ali Çehreli wrote:
>>> What I and many others who say Errors should not be caught are saying
>>> is, once the program is in an unexpected state, attempting to do
>>> anything further is wishful thinking.
>>
>> I've been thinking about this a bit more, and I'm curious: how do you
>> recommend that an application behave when an Error is thrown?
> It has lost its face and shall commit sucide.
> That's the japanese way, and it has its merits.
> Continuing to work and pretend nothing has happened (the european way)
> makes it just untrustworthy from the begining.

https://github.com/munificent/vigil is the programming language for you.


More information about the Digitalmars-d mailing list