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

My HSQLDB schema inspection story

This is a simple story of my need to inspect the schema of an HSQLDB database for a participar FOREIGN KEY, and the interesting things I had to do to actually inspect it. I am using an HSQLDB 1.8 database in one of my web applications. The application has been developed using the Play framework , which by default uses JPA and Hibernate . A few days back, I wanted to inspect the schema which Hibernate had created for one of my model objects. I started the HSQLDB database on my local machine, and then started the database manager with the following command java -cp ./hsqldb-1.8.0.7.jar org.hsqldb.util.DatabaseManagerSwing When I tried the view the schema of my table, it showed me the columns and column types on that table, but it did not show me columns were FOREIGN KEYs. Image 1: Table schema as shown by HSQLDB's database manager I decided to search on StackOverflow and find out how I could view the full schema of the table in question. I got a few hints, and they all pointed to

Commenting your code

Comments are an integral part of any program, even though they do not contribute to the logic. Appropriate comments add to the maintainability of a software. I have heard developers complain about not remembering the logic of some code they wrote a few months back. Can you imagine how difficult it can be to understand programs written by others, when we sometimes find it hard to understand our own code. It is a nightmare to maintain programs that are not appropriately commented. Java classes should contain comments at various levels. There are two types of comments; implementation comments and documentation comments. Implementation comments usually explain design desicisions, or a particularly intricate peice of code. If you find the need to make a lot of implementation comments, then it may signal overly complex code. Documentation comments usually describe the API of a program, they are meant for developers who are going to use your classes. All classes, methods and variables

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other