Java: Exception
•Download as PPT, PDF•
9 likes•2,555 views
Sub: Java Topic: Exception Slide number: 6 Presented by: Mahbubul Islam (MMI) Lecturer, Dept. of CSE University of Rajshahi
![Exceptions ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Java: Exception
Similar to Java: Exception (20)
More from Tareq Hasan
More from Tareq Hasan (20)
Recently uploaded
Recently uploaded (20)
Java: Exception
- 1. Exception
- 7. Throwable Error Exception Runtime Exception IO Exception The Java Exception Hierarchy
- 33. The MathMistake class
- 34. Output of the Attempted Execution of the MathMistake Application
- 39. Format of try...catch Pair
- 41. The MathMistakeCaught Application
- 43. The TwoMistakes Class
- 44. The TwoMistakes2 Class
- 47. Format of try...catch...finally Sequence
- 52. Pseudocode Representing Traditional Error Checking
- 54. Pseudocode Representing Object-Oriented Exception Handling
- 56. The PriceList Class
- 62. Cycling Through the Call Stack
Editor's Notes
- Runtime exceptions make it impossible to know what exceptions can be emitted by a method. They also result in incosistent throws decls among developers. Describe subsumption to people: subsumption is often how IOException derivatives are dealt with (subsumption is casting to the base class). The most vituperative debate is between those who believe unchecked exceptions make mechanical testing nearly impossible, and those who believe that checked exceptions impinge on polymorphism by making the exception list part of the method signature (and thereby inheritable).
- The top example comes from the JDK documentation.
- This is a perfect demonstration of why there are unchecked exceptions. It is likely that 99% of the time this method is called, there will be no problem. However, because the exception is checked, it must always be handled!
- The following resources must be managed explicitly: graphics contexts, file handles, sockets ,Windows, Image, and jdbc resources.
- be careful about the close() method raising an exception.
- The ‘end of while’ statement is never reached. finally blocks can alter the return value, even if a return was what caused the finally block to be invoked. finally blocks can manage all transfers of control…
- From the Java Language Spec.