|Prev 16||Concurrency and Java||Chapter 13 not sect'n 9||lab16 Java102|
|17||Exceptions||Chapter 14||lab17 Java103|
|Next 18||Prolog||Chapter 2 sect'n 13 + Prolog Handout||lab18 Prolog101|
Key ideas to remember:
The CSci202 book "Scansholm" and Bjarne Stroustroup's LRM make a useful reference for C++ programmers. They won't be on the final.
Exception Handling Principles
Notes on Chapter 14
Event handling arrived late in the computer languages but is now a vital
part of programming(Section 14.6.2...). GUIs (14.6.1) are easier than they
Exceptions are not a late arrival. They are natural way to cope with Murphy's Law: If anything can go wrong, it will.
Note. History of C++/Java exceptions. The throw and catch terminology comes form ..... CLOS LISP.
Exceptions in Java (Missing point in book)
The book does not mention a property of RuntimeException in Java. Normally
the compiler rejects code that fails to catch a thrown Exception and
doesn't declare that it throws it. This is not true of RuntimeExceptions. A
welcome relief. You should spend some time in next sessions's lab exploring
the Throwable hierarchy
[ Throwable.html ]
in Sun's documentation.