Pure Programmer
Blue Matrix


Cluster Map

Exception Handling

L1

This page is under construction. Please come back later.

Many functions take in arguments, do a computation and return a result without any diffuculties. But some functions may run into problems that need to be reported to the calling code. Problems can be found in the arguments being passed, with system resources that are not available or with computations that just can't be performed. Returning an error code through the formal return value of a function is one technique but it requires the calling code to check the result of a function to see if the error code was returned. Often this step is omitted resulting in bad values being propogated through the code. A better approach is to have the function throw an exception. An exception is just an object that is returned through the alternate exceptional return mechanism instead of the normal return mechanism. In the following example the stoi() and stof() functions could fail if the string passed can't be converted to a number. In the case of stoi() this function returns numbers across the whole range of integers so there is no value that can be returned to indicate an error that is not also a valid integer. This is why these two functions return a value if they can and if they can not, they throw an exception. Because the code below doesn't check for execptions being thrown, it will simply quit and print an error message detailing the exception thrown if bad input is passed to either of the two functions.

Exceptions1.java
import org.pureprogrammer.Utils;

public class Exceptions1 {

	public static void main(String[] args) {
		int i;
		double d;
		i = Integer.parseInt(args[0]);
		d = Double.parseDouble(args[1]);
		System.out.println(Utils.format("i + d = {0:f}", i + d));
	}
}

Output
$ javac -Xlint Exceptions1.java $ java -ea Exceptions1 1 3.1415926 i + d = 4.141593 $ javac -Xlint Exceptions1.java $ java -ea Exceptions1 1 abc Exception in thread "main" java.lang.NumberFormatException: For input string: "abc" at java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2054) at java.base/jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110) at java.base/java.lang.Double.parseDouble(Double.java:651) at Exceptions1.main(Exceptions1.java:9) $ javac -Xlint Exceptions1.java $ java -ea Exceptions1 abc 3.1415926 Exception in thread "main" java.lang.NumberFormatException: For input string: "abc" at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67) at java.base/java.lang.Integer.parseInt(Integer.java:668) at java.base/java.lang.Integer.parseInt(Integer.java:786) at Exceptions1.main(Exceptions1.java:8)

In the example below we add exception handling code around each of the two functions that can throw. This is done useing a try/catch construct. The try block wraps the code that might throw an exception. Following the try block is a catch block that contains the error handling code that is only executed if an exception is thrown in the preceding try block. When an exception is thrown, the try block is terminated immediately and control passes to the catch block. If no exception is thrown, all the code in the try block is executed and the catch block is skipped. The example below illustrates what will happen with good input and some bad input.

Exceptions2.java
import org.pureprogrammer.Utils;

public class Exceptions2 {

	public static void main(String[] args) {
		int i = 0;
		double d = 0;
		try {
			i = Integer.parseInt(args[0]);
		} catch (Exception ex) {
			System.out.println("Can't convert to integer!");
			System.exit(1);
		}
		try {
			d = Double.parseDouble(args[1]);
		} catch (Exception ex) {
			System.out.println("Can't convert to floating point!");
			System.exit(1);
		}
		System.out.println(Utils.format("i + d = {0:f}", i + d));
	}
}

Output
$ javac -Xlint Exceptions2.java $ java -ea Exceptions2 1 3.1415926 i + d = 4.141593 $ javac -Xlint Exceptions2.java $ java -ea Exceptions2 1 abc Can't convert to floating point! $ javac -Xlint Exceptions2.java $ java -ea Exceptions2 abc 3.1415926 Can't convert to integer!

As this code illustrates, exception handling allows use to possibly recover from an error or at a minimum, present a more meaningful error message to the user and then terminate the program in an orderly fashion.

The example above illustrates one way to deal with exceptions, namely providing a try/catch construct to wrap each and every function that might throw. While this a very fine-grained approach that gives us lots of control, it can become tedious if many functions that can throw are being used. Another approach is presented below whereby all the core logic of our main code is wrapped in a single try/catch. If any of the functions in main throw an exception it will cause control flow to immediately jump into the catch handler. This approach requires less exception handling code but sometimes prevents us from knowing exactly which function had a problem that required it to throw an exception.

Exceptions3.java
import org.pureprogrammer.Utils;

public class Exceptions3 {

	public static void main(String[] args) {
		int i = 0;
		double d = 0;
		try {
			i = Integer.parseInt(args[0]);
			d = Double.parseDouble(args[1]);
			System.out.println(Utils.format("i + d = {0:f}", i + d));
		} catch (Exception ex) {
			System.out.println("Can't convert command line argument!");
		}
	}
}

Output
$ javac -Xlint Exceptions3.java $ java -ea Exceptions3 1 3.1415926 i + d = 4.141593 $ javac -Xlint Exceptions3.java $ java -ea Exceptions3 1 abc Can't convert command line argument! $ javac -Xlint Exceptions3.java $ java -ea Exceptions3 abc 3.1415926 Can't convert command line argument!
Exceptions4.java
import org.pureprogrammer.Utils;

public class Exceptions4 {

	public static void main(String[] args) {
		int i = 0;
		double d = 0;
		try {
			i = Integer.parseInt(args[0]);
			d = Double.parseDouble(args[1]);
			System.out.println(Utils.format("i + d = {0:f}", i + d));
		} catch (NumberFormatException ex) {
			System.out.println("Can't convert command line argument!");
		} catch (Exception ex) {
			System.out.println("Don't know what went wrong!");
		}
	}
}

Output
$ javac -Xlint Exceptions4.java $ java -ea Exceptions4 1 3.1415926 i + d = 4.141593 $ javac -Xlint Exceptions4.java $ java -ea Exceptions4 1 abc Can't convert command line argument! $ javac -Xlint Exceptions4.java $ java -ea Exceptions4 abc 3.1415926 Can't convert command line argument!
Exceptions5.java
import org.pureprogrammer.Utils;

public class Exceptions5 {

	public static void main(String[] args) {
		int i = 0;
		double d = 0;
		try {
			i = Integer.parseInt(args[0]);
			d = Double.parseDouble(args[1]);
			System.out.println(Utils.format("i + d = {0:f}", i + d));
		} catch (NumberFormatException ex) {
			System.out.println("Can't convert command line argument!");
		} catch (Exception ex) {
			System.out.println("Don't know what went wrong!");
		} finally {
			System.out.println("This statement always executes.");
		}
	}
}

Output
$ javac -Xlint Exceptions5.java $ java -ea Exceptions5 1 3.1415926 i + d = 4.141593 This statement always executes. $ javac -Xlint Exceptions5.java $ java -ea Exceptions5 1 abc Can't convert command line argument! This statement always executes. $ javac -Xlint Exceptions5.java $ java -ea Exceptions5 abc 3.1415926 Can't convert command line argument! This statement always executes.
java

Questions

Projects

More ★'s indicate higher difficulty level.

References