ctrl+c and destructors

[nazriel]

On Thursday, 3 October 2013 at 20:54:00 UTC, Walter Bright wrote:
> On 10/3/2013 1:02 AM, Max Samukha wrote:
>> That famous prejudice of yours :).
>
> Not just me, and I didn't invent it. It's a "prejudice" used by 
> experienced engineers who build things that, if they fail, kill 
> people. That prejudice is relearned, over and over, by bitter 
> experience.
>

Music player (as example) do not kill people if they fail.
Aborting whole music player just because Visualisation plugin had 
access violation is pointless.

You can't put every use case into the same bag...

>> As always, it depends. The application can't
>> "recover" but it can give the user an opportunity to 
>> (partially) recover his
>> work. For example, I appreciated the fact that Cubase/Nuendo 
>> often continued
>> execution after a poorly debugged in-process plugin 
>> segfaulted. I do not know
>> exactly what cleanup procedure the application executed on the 
>> inconsistent
>> state but most of the time I was able to recover it completely.
>
> You've got a badly designed program if it relies on that to 
> recover user data.