Home/ Questions/Q 6140093
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T18:04:25+00:00

Is there any reason for not converting the following code try { // Do

  • 0

Is there any reason for not converting the following code

try {
    // Do something
} catch (XException e) {
    e.printStackTrace();
} catch (YException e) {
    e.printStackTrace();
} catch (ZException e) {
    e.printStackTrace();
}

to this:

try {
    // Do something
} catch (Exception e) {
    e.printStackTrace();
}

I know the 2nd one catches all kinds of Exceptions, and I don’t mind that. And let’s say I want to handle all exceptions in the same way. Is the performance difference considerable?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The Java try/catch mechanism has been so highly tuned in successive JVM’s that their performance is never something you should be explicitely worried about. Rather, you should be coding those blocks according to whether you need to handle the caught error scenarios in different ways. In your example you are just printing a stack trace so it is not beneficial to catch the specific errors – but your use case will actually determine wether you should be rolling up or down for these try/catch blocks.

    • 0