Scribd
Upload
8 views

Unit 4.1 - Exceptions in Java

Java

Uploaded by

Aryan Gireesh
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
8 views

Unit 4.1 - Exceptions in Java

Java

Uploaded by

Aryan Gireesh
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

Exceptions in Java

What is an exception?
● An exception is an error condition that changes the
normal flow of control in a program
● Exceptions in Java separates error handling from main
business logic
● Based on ideas developed in Ada, Eiffel and C++
● Java has a uniform approach for handling all
synchronous errors
∙ From very unusual (e.g. out of memory)
∙ To more common ones your program should check itself (e.g.
index out of bounds)
∙ From Java run-time system errors (e.g., divide by zero)
∙ To errors that programmers detect and raise deliberately
Throwing and catching

● An error can throw an exception


throw <exception object>;
● By default, exceptions result in the thread
terminating after printing an error message
● However, exception handlers can catch specified
exceptions and recover from error
catch (<exception type> e) {
//statements that handle the exception
}
Exceptional flow of control

● Exceptions break the normal flow of control.


● When an exception occurs, the statement that
would normally execute next is not executed.
● What happens instead depends on:
– whether the exception is caught,
– where it is caught,
– what statements are executed in the ‘catch block’,
– and whether you have a ‘finally block’.
Approaches to handling an exception

1. Prevent the exception from happening


2. Catch it in the method in which it occurs, and either
a. Fix up the problem and resume normal execution
b. Rethrow it
c. Throw a different exception
3. Declare that the method throws the exception
4. With 1. and 2.a. the caller never knows there was an
error.
5. With 2.b., 2.c., and 3., if the caller does not handle the
exception, the program will terminate and display a
stack trace
Exception hierarchy

● Java organizes exceptions in inheritance tree:


– Throwable
– Error
– Exception
● RuntimeException
● TooManyListenersException
● IOException
● AWTException
Error and RuntimeException

● Error
– “unchecked”, thus need not be in ‘throws’ clause
– Serious system problems (e.g. ThreadDeath, OutOfMemoryError)
– It’s very unlikely that the program will be able to recover, so
generally you should NOT catch these.
● RuntimeException
– “unchecked”, thus need not be in ‘throws’ clause
– Also can occur almost anywhere, e.g. ArithmeticException,
NullPointerException, IndexOutOfBoundsException
– Try to prevent them from happening in the first place!
● System will print stop program and print a trace
Java is strict
● Unlike C++, is quite strict about catching exceptions
● If it is a checked exception
– (all except Error, RuntimeException and their subclasses),
– Java compiler forces the caller must either catch it
– or explicitly re-throw it with an exception specification.
● Why is this a good idea?
● By enforcing exception specifications from top to bottom,
Java guarantees exception correctness at compile time.
● Here’s a method that ducks out of catching an exception by
explicitly re-throwing it:
void f() throws tooBig, tooSmall, divZero {
– The caller of this method now must either catch these
exceptions or rethrow them in its specification.
Catching an exception
try { // statement that could throw an exception
}
catch (<exception type> e) {
// statements that handle the exception
}
catch (<exception type> e) { //e higher in hierarchy
// statements that handle the exception
}
finally {
// release resources
}
//other statements
● At most one catch block executes
● finally block always executes once, whether there’s an error or
not
Execution of try catch blocks
● For normal execution:
– try block executes, then finally block executes, then other statements execute
● When an error is caught and the catch block throws an exception or returns:
– try block is interrupted
– catch block executes (until throw or return statement)
– finally block executes
● When error is caught and catch block doesn’t throw an exception or return:
– try block is interrupted
– catch block executes
– finally block executes
– other statements after catch executes
● When an error occurs that is not caught:
– try block is interrupted
– finally block executes
Catch processing
● When an exception occurs, the nested try/catch statements are
searched for a catch parameter matching the exception class
● A parameter is said to match the exception if it:
– is the same class as the exception; or
– is a superclass of the exception; or
– if the parameter is an interface, the exception class implements the
interface.
● The first try/catch statement that has a parameter that matches
the exception has its catch statement executed.
● After the catch statement executes, execution resumes with the
finally statement, then the statements after the try/catch
statement.
Catch processing example
print("now");
try
{ print("is ");
throw new MyException();
print("a ");
}
catch(MyException e) { print("the "); }
print("time\n");
● Prints "now is the time".
● Note that exceptions don't have to be used only for error handling
● Would it be a good idea to exceptions for non-error processing?
● But any other use is likely to result in code that's hard to understand.
Declaring an exception type
● Inherit from an existing exception type.
● Provide a default constructor
● and a constructor with one arg, type String.
● Both should call super(astring);
● Example:

class MyThrowable extends Throwable {


// checked exception
MyThrowable () {
super ("Generated MyThrowable");
}
MyThrowable (String s) { super (s); }
}
Declaring an exception type

● Inherit from an existing exception type.


● Provide a default constructor
● and a constructor with one arg, type String.
● Both should call super(astring);
class ErrorThrower {
public void errorMethod() throws MyThrowable
{ throw new MyThrowable ("ErrorThrower");
// forces this method to declare MyThrowable
}
}
Exceptions are ubiquitous in Java

● Exception handling required for all read methods


– Also many other system methods
● If you use one of Java's built in class methods and
it throws an exception, you must catch it (i.e.,
surround it in a try/catch block) or rethrow it, or you
will get a compile time error:
char ch;
try { ch = (char) System.in.read(); }
catch (IOException e)
{ System.err.println(e); return;
Assertion:

● Assertion is a statement in java. It can be


used to test your assumptions about the
program.
● While executing assertion, it is believed to be
true. If it fails, JVM will throw an error named
AssertionError.
● It is mainly used for testing purpose.
Advantage of Assertion:

● It provides an effective way to detect and correct


programming errors.
● Syntax of using Assertion:
There are two ways to use assertion. First way is:
– assert expression;
and second way is:
– assert expression1 : expression2;

You might also like