I’ve seen this in production code before. I might argue if you caught a very specific exception type that didn’t matter it might be acceptable. Maybe. But just the overall Exception type… Recipe for disaster.
What really sucks, imho, is that lazy programmers won in java’s checked exception wars.
With checked exceptions you have to type a little more, but it means that you can be sure you caught every exception type.
By making everything into a runtime exception you never know if you caught all relevant types of exceptions.
Which then again leads to people blanket-catching Exception because that way the app will at least not randomly crash due to a forgotten catch for some obscure exception type.
It’s a trash solution for a trash problem caused by lazyness even though there was a real solution available all along.
try { execute.SomeMethod(); } catch(Exception ex) {}I’ve seen this in production code before. I might argue if you caught a very specific exception type that didn’t matter it might be acceptable. Maybe. But just the overall Exception type… Recipe for disaster.
What really sucks, imho, is that lazy programmers won in java’s checked exception wars.
With checked exceptions you have to type a little more, but it means that you can be sure you caught every exception type.
By making everything into a runtime exception you never know if you caught all relevant types of exceptions.
Which then again leads to people blanket-catching
Exceptionbecause that way the app will at least not randomly crash due to a forgotten catch for some obscure exception type.It’s a trash solution for a trash problem caused by lazyness even though there was a real solution available all along.
goto fail;