Exception Handling and Format output

1. Exception Handlingand Format output

2. Midterm exam • Date: Oct 31 • Content: Week 1 to Week 8 Format: Multiple choice Determine the results of the code Write simple code

3. Introduction • Exception – an indication of a problem that occurs during a program’s execution • Exception handling – resolving exceptions that may occur so program can continue or terminate gracefully • Exception handling enables programmers to create programs that are more robust and fault-tolerant

4. Introduction • Examples • ArrayIndexOutOfBoundsException – an attempt is made to access an element past the end of an array • NullPointerException – when a null reference is used where an object is expected

5. Exception-Handling Overview • Intermixing program logic with error-handling logic can make programs difficult to read, modify, maintain and debug • Exception handling enables programmers to remove error-handling code from the “main line” of the program’s execution • Improves clarity • Enhances modifiability

6. String inputStr; int age; inputStr = JOptionPane.showInputDialog(null, "Age:"); age = Integer.parseInt(inputStr); Example: Not Catching Exceptions Error message for invalid input Exception in thread "main" java.lang.NumberFormatException: For input string: "ten" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at Week7.SimpleException.main(SimpleException.java:12)

7. inputStr = JOptionPane.showInputDialog(null, "Age:"); try{ age = Integer.parseInt(inputStr); }catch(NumberFormatException e){ JOptionPane.showMessageDialog(null, "’" + inputStr + "‘ is invalid\n" + "Please enter digits only"); } try catch Catching an Exception

8. Performance Tip If the potential problems occur infrequently, intermixing program and error-handling logic can degrade a program’s performance, because the program must perform (potentially frequent) tests to determine whether the task executed correctly and the next task can be performed.

9. Try-catch: what does that mean? When an exception occurs, or is thrown, the normal sequence of flow is terminated. The exception-handling routine is then executed; we say the thrown exception is caught.

10. Try-catch: what does that mean? • try block – encloses code that might throw an exception and the code that should not execute if an exception occurs • Consists of keyword try followed by a block of code enclosed in curly braces

11. Try-catch: what does that mean? • catch block – catches (i.e., receives) and handles an exception, contains: • Begins with keyword catch • Exception parameter in parentheses – exception parameter identifies the exception type and enables catch block to interact with caught exception object • Block of code in curly braces that executes when exception of proper type occurs

12. Try-catch: what does that mean? • Matching catch block – the type of the exception parameter matches the thrown exception type exactly or is a superclass of it • Uncaught exception – an exception that occurs for which there are no matching catch blocks • Cause program to terminate if program has only one thread; Otherwise only current thread is terminated and there may be adverse effects to the rest of the program

13. try-catch Control Flow

14. try-catch Control Flow • When an exception occurs: • try block terminates immediately • Program control transfers to first matching catch block • After exception is handled: • Termination model of exception handling – program control does not return to the throw point because the try block has expired; Flow of control proceeds to the first statement after the last catch block • Resumption model of exception handling – program control resumes just after throw point

15. try-catch Control Flow • try statement – consists of try block and corresponding catch and/or finally blocks Logic errors can occur if you assume that after an exception is handled, control will return to the first statement after the throw point.

16. Tip With exception handling, a program can continue executing (rather than terminating) after dealing with a problem. This helps ensure the kind of robust applications that contribute to what is called mission-critical computing or business-critical computing.

17. Review To catch an exception, code must be enclosed in a a. throws block. b. catch block. c. try block. d. finally block.

18. Review To catch an exception, code must be enclosed in a a. throws block. b. catch block. c. try block. d. finally block.

19. Review An uncaught exception: a. is a possible exception that never actually occurs during the execution of the program. b. is an exception that occurs for which the matching catch clause is empty. c. is an exception that occurs for which there are no matching catch clauses. d. is another term for a thrown exception

20. Review An uncaught exception: a. is a possible exception that never actually occurs during the execution of the program. b. is an exception that occurs for which the matching catch clause is empty. c. is an exception that occurs for which there are no matching catch clauses. d. is another term for a thrown exception

21. try{ . . . }catch (NumberFormatException e){ System.out.println(e.getMessage()); e.printStackTrace(); } Getting Information • There are two methods we can call to get information about the thrown exception: • getMessage • printStackTrace

22. printStackTrace, getStackTrace and getMessage • Methods in class Throwable retrieve more information about an exception • printStackTrace – outputs stack trace to standard error stream • getStackTrace – retrieves stack trace information as an array of StackTraceElement objects; enables custom processing of the exception information • getMessage – returns the descriptive string stored in an exception

23. try { . . . age = Integer.parseInt(inputStr); // Asuming I have a file I/O here . . . }catch (NumberFormatException e){ . . . } catch(FileNotFoundException file_error){ . . . } Multiple catch Blocks • A single try-catch statement can include multiple catch blocks, one for each type of exception.

24. Multiple catch Control Flow

25. The finally Block • There are situations where we need to take certain actions regardless of whether an exception is thrown or not. • We place statements that must be executed regardless of exceptions in the finally block.

26. try-catch-finally Control Flow

27. publicint getAge( )throws NumberFormatException { . . . int age = Integer.parseInt(inputStr); . . . return age; } Propagating Exceptions • Instead of catching a thrown exception by using the try-catch statement, we can propagate the thrown exception back to the caller of our method. • The method header includes the reserved word throws.

28. publicvoid doWork(intnum)throws Exception { . . . if (num != val) throw new Exception("Invalid val"); . . . } Throwing Exceptions • We can write a method that throws an exception directly, i.e., this method is the origin of the exception. • Use the throw reserved to create a new instance of the Exception or its subclasses. • The method header includes the reserved word throws.

29. Sample Call Sequence

30. Exception Thrower • When a method may throw an exception, either directly or indirectly, we call the method an exception thrower. • Every exception thrower must be one of two types: • catcher. • propagator.

31. Review Which of the following is not true regarding the throw point of an exception? a. It specifies the point at which the exception must be handled. b. It is the initial point at which the exception occurs. c. It is specified as the top row of the method-call stack at the time the exception occurred. d. All of the above statements are true.

32. Review Which of the following is not true regarding the throw point of an exception? a. It specifies the point at which the exception must be handled. b. It is the initial point at which the exception occurs. c. It is specified as the top row of the method-call stack at the time the exception occurred. d. All of the above statements are true.

33. Review Which of the following is not true regarding the throw point of an exception? a. It specifies the point at which the exception must be handled. b. It is the initial point at which the exception occurs. c. It is specified as the top row of the method-call stack at the time the exception occurred. d. All of the above statements are true.

34. Review question Which of the following statements is not true? a. Exception handling enables programmers to write robust and fault-tolerant programs. b. Exception handling can only catch the exception but cannot resolve the exception. c. Exception handling can resolve exceptions. d. The Java 2 Platform, Standard Edition, Version 1.4 introduced the new chained exception feature.

35. Review question Which of the following statements is not true? a. Exception handling enables programmers to write robust and fault-tolerant programs. b. Exception handling can only catch the exception but cannot resolve the exception. c. Exception handling can resolve exceptions. d. The Java 2 Platform, Standard Edition, Version 1.4 introduced the new chained exception feature.

36. Debugging 101 • execute your Java program line by line • examine the value of variables at different points in the program How to do: set a breakpoint in your code so the debugger suspends execution (double-click in the gray margin on the left side of the editor ) choose Run -> Debug As -> Java Applications

37. Types of Exception Throwers • An exception catcher is an exception thrower that includes a matching catch block for the thrown exception. • An exception propagator does not contain a matching catch block. • A method may be a catcher of one exception and a propagator of another.

38. Using the throws Clause • throws clause – specifies the exceptions a method may throws • Appears after method’s parameter list and before the method’s body • Contains a comma-separated list of exceptions • Exceptions can be thrown by statements in method’s body of by methods called in method’s body • Exceptions can be of types listed in throws clause or subclasses

39. When to Use Exception Handling • Exception handling designed to process synchronous errors • Synchronous errors – occur when a statement executes • Asynchronous errors – occur in parallel with and independent of the program’s flow of control

40. Java Exception Hierarchy • All exceptions inherit either directly or indirectly from class Exception • Exception classes form an inheritance hierarchy that can be extended • Class Throwable, superclass of Exception • Only Throwable objects can be used with the exception-handling mechanism • Has two subclasses: Exception and Error • Class Exception and its subclasses represent exception situations that can occur in a Java program and that can be caught by the application • Class Error and its subclasses represent abnormal situations that could happen in the JVM – it is usually not possible for a program to recover from Errors

41. Portion of class Throwable’s inheritance hierarchy.

42. Checked/Compiling vs. Unchecked/Running time • There are two types of exceptions: • Checked/Compiling time • Unchecked/Run time • A checked exception is an exception that is checked at compile time. • All other exceptions are unchecked, or runtime, exceptions. As the name suggests, they are detected only at runtime.

43. Different Handling Rules • When calling a method that can throw checked exceptions • use the try-catch statement and place the call in the try block, or • modify the method header to include the appropriate throws clause. • When calling a method that can throw runtime exceptions, it is optional to use the try-catch statement or modify the method header to include a throws clause.

44. Handling Checked/Compiling Exceptions

45. Handling Unchecked/Runtime Exceptions

46. Java Exception Hierarchy • Two categories of exceptions: checked and unchecked • Checked exceptions • Exceptions that inherit from class Exception but not from RuntimeException • Compiler enforces a catch-or-declare requirement • Compiler checks each method call and method declaration to determine whether the method throws checked exceptions. If so, the compiler ensures that the checked exception is caught or is declared in a throws clause. If not caught or declared, compiler error occurs.

47. Java Exception Hierarchy • Unchecked exceptions • Inherit from class RuntimeException or class Error • Compiler does not check code to see if exception is caught or declared • If an unchecked exception occurs and is not caught, the program terminates or runs with unexpected results • Can typically be prevented by proper coding

48. Java Exception Hierarchy • catch block catches all exceptions of its type and subclasses of its type • If there are multiple catch blocks that match a particular exception type, only the first matching catch block executes • It makes sense to use a catch block of a superclass when all the catch blocks for that class’s subclasses will perform the same functionality

49. Outline

50. Review Exceptions can occur: a. from the Java Virtual Machine. b. through explicitly mentioned code in a try block. c. through calls to other methods made in a try block. d. All of the above.