title: Multiple or Single Try Catch
body: <p>I'm working on cleaning up some of my code and I came to a point where I wasn't sure which route would be better.</p>
  
  <p>Currently I have a single try catch block over the majority of my method and it handles a few separate exceptions at the end, but I figured having more try catch blocks would be better just for maintenance. However, while breaking down the code I came to a point where I was writing multiple blocks for the same type of exception. I can see the up side to writing a block for each part since I can then give more specifics to why it failed.</p>
  
  <p>My question is this... is there a downside to doing this? Could there be performance issues or some other hidden monster that I'm not seeing?</p>
  
  <p>Also, what is the preferred way of handling multiple exceptions in a method, is there an industry standard?  </p>
  
  <p>Just to better illustrate my point here's some pseudo code</p>
  
  <pre><code>//multiple try catch for same exception
  try {
       //some code here
  } catch (MyException e) {
       //specific error message here
  }
  try {
       //some different code here
  } catch (MyException e) {
       //more specific error message indicating a different issue
  }
  </code></pre>