Skip to main content

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.

2
  • 6
    Why do you want to know which exceptions might be thrown? It's extremely rare that you should catch exceptions, so the need to know the specific type is similarly rare; meanwhile, you should assume that exceptions could be thrown at almost any point, e.g. range checking, floating point, access violation from nil pointer uses, etc.
    – Barry Kelly
    Commented Jan 28, 2011 at 15:52
  • 2
    @Barry: There might be several reasons (1) Maybe I want to catch an exception and throw another one (more appropriate one) (2) I might want to show different error dialogs to the user (or no error dialog depending on the context). I'm not talking about unexpected exceptions like access violations and the kind.
    – jpfollenius
    Commented Jan 31, 2011 at 7:38