Brilliant exception handling I found in an app i had to work on
2 points
*
wait what ?
So you are saying that the following code will keep throwing e
but if I used throw e;
it would basically be the same except for the stack trace that would be missing the important root cause ?!
try {
} catch (WhateverException e) {
// stuff, or nothing, or whatever
throw;
}