You saw in Section 7.10 that exceptions are processed by catch
handlers. At least one catch
handler (lines 37–41) must immediately follow each try
block. An exception parameter should always be declared as a reference to the type of exception the catch
handler can process (DivideByZeroException
in this case)—this prevents copying the exception object when it’s caught and allows a catch handler to properly catch derived-class exceptions as well. When an exception occurs in a try
block, the catch
handler that executes is the first one whose type matches the type of the exception that occurred (i.e., the type in the catch
block matches the thrown exception type exactly or is a direct or indirect base class of it). If an exception parameter includes an optional parameter name, the catch
handler can use that parameter name to interact with the caught exception in the body of the catch
handler, which is delimited by braces ({
and }
). A catch
handler typically reports the error to the user, logs it to a file, terminates the program gracefully or tries an alternate strategy to accomplish the failed task. In this example, the catch
handler simply reports that the user attempted to divide by zero. Then the program prompts the user to enter two new integer values.
Common Programming Error 17.1
It’s a syntax error to place code between a try block and its corresponding catch handlers or between its catch handlers.
Common Programming Error 17.2
Each catch handler can have only a single parameter—specifying a comma-separated list of exception parameters is a syntax error.
Common Programming Error 17.3
It’s a compilation error to catch the same type in multiple catch handlers following a single try block.
3.145.44.199