Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • 4
    possible duplicate? When to throw an exception. Though it was closed there, but I think it fits here. It's still a bit of philosophy, some people and communities tend to see exceptions as a kind of flow control. Commented Jan 24, 2013 at 8:58
  • 8
    When users are dumb, they provide invalid input. When users are smart, they play by providing invalid input. Therefore, invalid user input is not an exception. Commented Jan 24, 2013 at 12:10
  • 7
    Also, don't confuse an exception, which is a very specific mechanism in Java and .NET, with an error which is a much more generic term. There's more to error handling than throwing exceptions. This discussion touches on the nuances between exceptions and errors. Commented Jan 24, 2013 at 14:39
  • 4
    "Exceptional" != "Rarely Happens" Commented Jan 24, 2013 at 17:30
  • 3
    I find Eric Lippert's Vexing exceptions to be decent advice. Commented Nov 19, 2013 at 14:02