Menu
Is this considered good programming practice in C++:
try {
// some code
}
catch(someException) {
// do something
}
catch (...)
{
// left empty <-- Good Practice???
}
716
It's considered best practice to put as little code as possible in each try / catch block. This means that you may need multiple try / catch blocks, instead of just one. The benefits of this are that: it's easy to see which code raises which exceptions (and which code doesn't raise exceptions)
Yes, it is limited to one try-catch in the same function.
This is not good programming practice in C++ or in any other language. Silent failures are bad and will bite you sooner or later. If you are going to catch (...) the very least you should do is log that you are doing it. You may also need to delete some objects if you are not using RAII.
throws: The throws keyword is used for exception handling without try & catch block. It specifies the exceptions that a method can throw to the caller and does not handle itself. 5. finally: It is executed after the catch block.
No! That is a terrible practice!
Just about the only time you should catch (...) and not rethrow the exception would be in main() to catch any otherwise unhandled exceptions and to display or log an error before exiting.
If you catch (...), you have absolutely no idea what exception was thrown, and thus you can't know whether it is safe to continue running.
110
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
