Ignoring (serious) errors to keep the program alive?

Posted by SQuirreL bites on Stack Overflow See other posts from Stack Overflow or by SQuirreL bites
Published on 2010-04-26T16:40:37Z Indexed on 2010/04/26 16:43 UTC
Read the original article Hit count: 191

One of the main things I wanted to achieve in my experimental programming language was: When errors occur (Syntax, Name, Type, etc.) keep the program running, no matter how serious or devastating it is. I know that this is probably very bad, but I just wanted something that doesn't kill itself on every error - I find it interesting what happens when a serious error occurs but the program continues.

  • Does this "paradigm" have a name? I mean expect for
  • How bad is it to do the above?
  • Are there programs in use out there that just follow: "Hey, this is a fatal, unexpected error - but you know what? I don't care!"?

© Stack Overflow or respective owner

Related posts about design-patterns

Related posts about interpreter