We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
Loading...
  1. Practice
  2. Java
  3. Exception Handling
  4. Java Exception Handling (Try-catch)
  5. Discussions

Java Exception Handling (Try-catch)

  • AdHominem + 7 comments

    Again a great example of how bad the test cases are written. Any professional would have caught the exceptions together and logged / souted them in a uniform way like this:

    try (Scanner scanner = new Scanner(System.in)) {
	System.out.println(scanner.nextInt()/scanner.nextInt());
} catch (ArithmeticException | InputMismatchException ex) {
	System.out.println(ex);
}

    This is best practise for any team I worked with and definitely the cleanest way to solve this. But thanks to the nitpicking test cases, beginners learn to catch exceptions in an utterly bloated way:

    try (Scanner scanner = new Scanner(System.in)) {
	System.out.println(scanner.nextInt()/scanner.nextInt());
} catch (ArithmeticException aex) {
	System.out.println(aex);
} catch (InputMismatchException imex) {
	System.out.println(imex.getClass().getName());
}
    • corney_hunter + 1 comment

      what is the difference between both ???

      • AdHominem + 0 comments

        They produce the same output, thats the problem. You can separate catch blocks IF you want to handle exceptions individually but if they are caught together, you can just use one catch block and catch all of them.

    • hackeranshu + 0 comments
      [deleted]
    • mssvai + 0 comments

      Thanks. I didn't know I can pass objects to try block.

      4th test case got failed tho, so I fixed it a lil bit.

      public static void main(String[] args)
{
    try(Scanner in = new Scanner(System.in))
    {
        System.out.println(in.nextInt()/in.nextInt());
    } catch(InputMismatchException ex)
    {
        System.out.println(ex.getClass().getName());
    }
    catch(ArithmeticException ae)
    {
        System.out.println(ae);
    }
}
    • 148W1A1237 + 0 comments

      Thank you brother. I have got it.

    • sb_pt + 0 comments

      Imagine people writing actual production code like this!

    • i140394 + 0 comments

      I learned a new thing :)

    • jonkenobi + 0 comments

      Thanks for sharing this info, as a beginner I see how much cleaner your code is instead of fitting the test examples.