Skip to main content

How do exceptions work?

Now let us understand how Exceptions work. The code shown below is a simple program that shows how to use Exceptions. Listen to the audio below as you view the code.


import java.io.*;

public class LearningExceptions {
  public static void main(String args[]) {
    LearningExceptions le = new LearningExceptions();
    System.out.println("Hello, this is a test program to
      understand Exceptions");
    try {
      System.out.print("Please enter your name: ");
      String name = le.getName();
      System.out.println("Hey " + name + " how are you doing?");
    catch(IOException ioe) {
      System.out.println("Looks like the standard input
        stream does not like you!");
    }
  }

  private String getName() throws IOException {
    BufferedReader br = new BufferedReader
      (new InputStreamReader(System.in));
    return(br.readLine());
  }
}
Java2html

 

Now let us compare how error handling is done with and without Exceptions. The PSEUDOCODE shown below has two methods: the first one is called aFunctionWithoutExceptions(), and the second one is called aFunctionWithExceptions(). As their names suggest the first method does error handling, the old way, by inspecting return values, and the second method does error handling with Exceptions.

//PSEUDOCODE
aFunctionWithoutExceptions() {
  doSomething1
  checkIfSomethingWentWrong
  doSomething2
  checkIfSomethingWentWrong
  doSomething3
  checkIfSomethingWentWrong
}

aFuntionWithExceptions() {
  try {
    doSomething1
    doSomething2
    doSomething3
  catch(ExceptionTypeA e1) {
    handle the exception
  catch(ExceptionTypeB e2) {
    handle the exception
  }
}
Java2html

 

When inspecting return values: 

  • We have to check for the return value after every function call. This increases code and also reduces readability of the code .
  • Error handling code is interspersed with program code.
  • Checking for the meaning of an error code will usually require long if...else statements.

When using Exceptions:

  •  We do not have to inspect the return value after every method call. We just invoke the method and if an Exception is thrown, control will automatically transfer to the appropriate Exception handling code.
  • Error handling code is in a distinct region (the catch block) and is not interspersed with program code.
  • We do not need to specifically check what an error code means. Since we throw unique Exceptions for unique problems, control will automatically be trasnferred to the appropriate catch block.
Note that we have two catch blocks in the second method. Whenever the statements in the try block are capale of throwing multiple Exceptions, we must catch all of them, either in a generic catch block that catches the superclass of all Exceptions "java.lang.Exception", or in individual catch blocks. It is advised to adopt the latter style.


Notes: This text was originally posted on my earlier blog at http://www.adaptivelearningonline.net

Comments

Popular posts from this blog

Running your own one person company

Recently there was a post on PuneTech on mom's re-entering the IT work force after a break. Two of the biggest concerns mentioned were : Coping with vast advances (changes) in the IT landscape Balancing work and family responsibilities Since I have been running a one person company for a good amount of time, I suggested that as an option. In this post I will discuss various aspects of running a one person company. Advantages: You have full control of your time. You can choose to spend as much or as little time as you would like. There is also a good chance that you will be able to decide when you want to spend that time. You get to work on something that you enjoy doing. Tremendous work satisfaction. You have the option of working from home. Disadvantages: It can take a little while for the work to get set, so you may not be able to see revenues for some time. It takes a huge amount of discipline to work without a boss, and without deadlines. You will not get the benefits (insuran

Testing Groovy domain classes

If you are trying to test Grails domain class constraints by putting your unit test cases in the 'test/unit' directory, then your tests will fail because the domain objects will not have the 'valdate' method. This can be resolved in two ways: Place the test cases inside test/integration (which will slow things down) Use the method 'mockForConstraintsTests(Trail)' to create mock method in your domain class and continue writing your test cases in 'test/unit' What follows is some example code around this finding. I am working on a Groovy on Grails project for a website to help programmers keep up and refresh their skills. I started with some domain classes and then moved on to write some unit tests. When we create a Grails project using grails create-app , it creates several directories, one of which is a directory called 'test' for holding unit tests. This directory contains two directories, 'unit', and 'integration' for uni

Some thoughts on redesigning education

Some time back I read a blog post on redesigning education. It asked some very good questions. Stuff which I had been thinking of myself. I left my thoughts on the blog, but I would also like to start a conversation around these ideas with those who read this blog as well. I would like to know what other people think of the issue of redesigning (college) education. I have often thought about how college education can be improved. To answer this question, we first have to ask a very basic question. What is the purpose of education? To me, we need education for 3 things: To learn more about the world around us To lead positive constructive lives To earn a good living / fulfill our ambitions I think education has to a large extent evolved to fulfill #3 (with a bias towards earning a comfortable living). The semester system, along with multiple choice tests, and grading, has made our education system into an assembly line. Students are pushed into the assembly line, given classes, admini