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

Fuctional Programming Principles in Scala - Getting Started

Sometime back I registered for the Functional Programming Principles in Scala , on Coursera. I have been meaning to learn Scala from a while, but have been putting it on the back burner because of other commitments. But  when I saw this course being offered by Martin Odersky, on Coursera , I just had to enroll in it. This course is a 7 week course. I will blog my learning experience and notes here for the next seven weeks (well actually six, since the course started on Sept 18th). The first step was to install the required tools: JDK - Since this is my work machine, I already have a couple of JDK's installed SBT - SBT is the Scala Build Tool. Even though I have not looked into it in detail, it seems like a replacement for Maven. I am sure we will use it for several things, however upto now I only know about two uses for it - to submit assignments (which must be a feature added by the course team), and to start the Scala console. Installed sbt from here , and added the path

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- prismnet.com As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a