I have a method that can throw two different exceptions, CommuncationException
and SystemException
. In both cases I do the same three-line code block.
try { ... } catch (CommunicationException ce) { ... } catch {SystemExcetion se) { ... }
Is there any possibility to do it like that?
try { ... } catch (CommunicationException ce, SystemException se) { ... }
Then I would not have to write this much code. I know I could extract the exception handling to a private method, but since the code is only 3 lines long, the method definition would take more code than the body itself.
In Java SE 7 and later, a single catch block can handle more than one type of exception. This feature can reduce code duplication and lessen the temptation to catch an overly broad exception.
If a catch block handles multiple exceptions, you can separate them using a pipe (|) and in this case, exception parameter (ex) is final, so you can't change it. The byte code generated by this feature is smaller and reduce code redundancy.
You can't throw two exceptions.
Yes, we can define one try block with multiple catch blocks in Java. Every try should and must be associated with at least one catch block.
If you can upgrade your application to C# 6 you are lucky. The new C# version has implemented Exception filters. So you can write this:
catch (Exception ex) when (ex is CommunicationException || ex is SystemException) { //handle it }
Some people think this code is the same as
catch (Exception ex) { if (ex is CommunicationException || ex is SystemException) { //handle it } throw; }
But it´s not. Actually this is the only new feature in C# 6 that is not possible to emulate in prior versions. First, a re-throw means more overhead than skipping the catch. Second, it is not semantically equivalent. The new feature preserves the stack intact when you are debugging your code. Without this feature the crash dump is less useful or even useless.
See a discussion about this on CodePlex. And an example showing the difference.
In fact, you could catch only SystemException
and it would handle CommunicationException
too, because CommunicationException
is derived from SystemException
catch (SystemException se) { ... //this handles both exceptions }
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