#881 – When to Throw Exceptions

Your code should throw an exception when

  • Something has gone wrong and your code cannot execute normally
  • You catch an exception and want to add some additional information
  • You catch an exception and your application cannot gracefully recover from the problem

Some examples of when you might throw an exception:

  • Parameter value that is out of range passed to a function
  • Parameter values that are inconsistent passed to a function
  • Invalid values passed to function (e.g. username with wrong password)
  • Function called while application is in the wrong state 

Do not throw exceptions

  • As part of normal operation, to control program flow
  • To return data back to code that called a function
  • Just to indicate which function was executing when an exception was caught

About Sean
Software developer in the Twin Cities area, passionate about .NET technologies. Equally passionate about my own personal projects related to family history and preservation of family stories and photos.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: