| << Chapter < Page | Chapter >> Page > |
Revised: Tue Mar 29 09:51:41 CDT 2016
This page is included in the following Books:
This module provides a very brief treatment of exception handling. The topic is discussed in detail in the module titled Java OOP: Exception Handling . The topic is included in this Programming Fundamentals section simply to introduce you to the concept.
I recommend that you open another copy of this module in a separate browser window and use the following link to easily find and view the listing while you are reading aboutit.
What is an exception?
According to The Java Tutorials , "An exception is an event that occurs during the execution of a program that disrupts the normal flow of instructions."
A very common example of an exception given in textbooks is code that attempts to divide by zero (this is easy to demonstrate) .
Throwing an exception
Common terminology states that when this happens, the system throws an exception . If a thrown exception is not caught , a runtime error may occur.
Purpose of exception handling
The purpose of exception handling is to make it possible for the program to either attempt to recover from the problem, or at worst shut down the program ina graceful manner, whenever an exception occurs.
Java supports exception handling
Java, C++, and some other programming languages support exception handling in similar ways.
In Java, the exception can be thrown either by the system or by code created by the programmer. Thereis a fairly long list of exceptions that will be thrown automatically by the Java runtime system.
Checked exceptions cannot be ignored
Included in that long list of automatic exceptions is a subset known as "checked" exceptions. Checked exceptions cannot be ignored by the programmer. A method must eitherspecify (declare) or catch all "checked" exceptions that can be thrown in order for the program to compile.
An example of specifying an exception
I explain the difference between specifying and catching an exception in Java OOP: Exception Handling . For now, suffice it to say that the code that begins with theword "throws" in Listing 1 specifies (declares) an exception that can be thrown by the code inside the main method.
If this specification is not made, the program will not compile.
| Listing 1 . The program named simple1. |
|---|
/*File simple1.java Copyright 1997, R.G.Baldwin
**********************************************************/class simple1 { //define the controlling class
public static void main(String[]args)
throws java.io.IOException {int ch1, ch2 = '0';
System.out.println("Enter some text, terminate with #");
//Get and save individual byteswhile( (ch1 = System.in.read() ) != '#') ch2 = ch1;
//Display the character immediately before the #System.out.println("The char before the # was "
+ (char)ch2);}//end main
}//End simple1 class. |
The program in Listing 1 does not throw any exceptions directly nor does it attempt to catch any exceptions. However, it can throw exceptions indirectly through itscall to System.in.read .
Because IOException is a checked exception, the main method must either specify it or catch it . Otherwise the program won't compile.In this case, the main method specifies the exception as opposed to catching it.
Very brief treatment
As mentioned earlier, this is a very brief treatment of a fairly complex topic that is discussed in much more detail in the module titled Java OOP: Exception Handling . The topic was included at this point simply to introduce you to the concept ofexceptions.
II encourage you to copy the code from Listing 1 . Compile the code and execute it. Experiment with the code,making changes, and observing the results of your changes. Make certain that you can explain why your changes behave as they do.
As you approach the end of this group of Programming Fundamentals modules, you should be preparing yourself for the more challenging ITSE 2321 OOPtracks identified below:
This section contains a variety of miscellaneous information.
Financial : Although the Connexions site makes it possible for you to download a PDF file for thismodule at no charge, and also makes it possible for you to purchase a pre-printed version of the PDF file, you should beaware that some of the HTML elements in this module may not translate well into PDF.
I also want you to know that, I receive no financial compensation from the Connexions website even if you purchase the PDF version of the module.
In the past, unknown individuals have copied my modules from cnx.org, converted them to Kindle books, and placed them for sale on Amazon.com showing me as the author. Ineither receive compensation for those sales nor do I know who does receive compensation. If you purchase such a book, please beaware that it is a copy of a module that is freely available on cnx.org and that it was made and published withoutmy prior knowledge.
Affiliation :: I am a professor of Computer Information Technology at Austin Community College in Austin, TX.
-end-
Notification Switch
Would you like to follow the 'Object-oriented programming (oop) with java' conversation and receive update notifications?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|