Catch(Exception) is always a good or bad idea

Question

Hi all, When we use catch exception is almost always a good or bad idea. Can anyone tell me.....

Jiteendra Sampathirao · Answer

hi, using the Catch(Exception) is pretty good idea.....

Nikos Rizos · Answer

I personally don't think it's good practice to solely rely on that in production. Any method or action that could cause an exception to be thrown should be handled at that stage (try..catch or passed to a custom handler class etc..). Not only does it make the application more robust, since you can handle specific exceptions in a way that is suitable to the situation, but it also makes it easier to find out why the exception is being thrown. There are many logging frameworks also available that make it easier to log exceptions and handle the errors.

Vulpes · Answer

It's usually better to narrow down the types of exception to catch and have a separate Catch clause for each exception type as they may need to be handled in a different way. However, sometimes this isn't necessary or practicable and other times you just want to have a general Catch clause to catch any remaining exceptions which haven't been caught by the specific Catch clauses. So, in those situations, the use of 'Catch Exception' is fine.

Catch(Exception) is always a good or bad idea

Answers (3)