The Objective-C language has an exception-handling syntax similar to that of Java and C++. Coupled with the use of the NSException, NSError, or custom classes, you can add robust error-handling to your programs. This article provides a summary of exception syntax and handling; for more details, see Exception Programming Topics.
Using GNU Compiler Collection (GCC) version 3.3 and later, Objective-C provides language-level support for exception handling. To turn on support for these features, use the -fobjc-exceptions switch of the GNU Compiler Collection (GCC) version 3.3 and later. (Note that this renders the application runnable only in Mac OS X v10.3 and later because runtime support for exception handling and synchronization is not present in earlier versions of the software.)
An exception is a special condition that interrupts the normal flow of program execution. There are a variety of reasons why an exception may be generated (exceptions are typically said to be raised or thrown), by hardware as well as software. Examples include arithmetical errors such as division by zero, underflow or overflow, calling undefined instructions (such as attempting to invoke an unimplemented method), and attempting to access a collection element out of bounds.
Objective-C’s exception support revolves around four compiler directives: @try, @catch, @throw, and @finally:
Code that can potentially throw an exception is enclosed in a @try block.
A @catch() block contains exception-handling logic for exceptions thrown in a @try block. You can have multiple @catch() blocks to catch different types of exception. (This is illustrated in “Catching Different Types of Exception.”)
A @finally block contains code that must be executed whether an exception is thrown or not.
You use the @throw directive to throw an exception, which is essentially an Objective-C object. You typically use an NSException object, but are not required to.
The example below depicts a simple exception-handling algorithm:
Cup *cup = [[Cup alloc] init]; |
@try { |
[cup fill]; |
} |
@catch (NSException *exception) { |
NSLog(@"main: Caught %@: %@", [exception name], [exception reason]); |
} |
@finally { |
[cup release]; |
} |
To catch an exception thrown in a @try block, use one or more @catch()blocks following the @try block. The @catch() blocks should be ordered from most-specific to the least-specific. That way you can tailor the processing of exceptions as groups, as shown in Listing 11-1.
Listing 11-1 An exception handler
@try { |
... |
} |
@catch (CustomException *ce) { // 1 |
... |
} |
@catch (NSException *ne) { // 2 |
// Perform processing necessary at this level. |
... |
} |
@catch (id ue) { |
... |
} |
@finally { // 3 |
// Perform processing necessary whether an exception occurred or not. |
... |
} |
The following list describes the numbered code-lines:
Catches the most specific exception type.
Catches a more general exception type.
Performs any clean-up processing that must always be performed, whether exceptions were thrown or not.
To throw an exception you must instantiate an object with the appropriate information, such as the exception name and the reason it was thrown.
NSException *exception = [NSException exceptionWithName:@"HotTeaException" |
reason:@"The tea is too hot" userInfo:nil]; |
@throw exception; |
Important: In many environments, use of exceptions is fairly commonplace. For example, you might throw an exception to signal that a routine could not execute normally—such as when a file is missing or data could not be parsed correctly. Exceptions are resource-intensive in Objective-C. You should not use exceptions for general flow-control, or simply to signify errors. Instead you should use the return value of a method or function to indicate that an error has occurred, and provide information about the problem in an error object. For more information, see Error Handling Programming Guide.
Inside a @catch() block, you can re-throw the caught exception using the @throw directive without an argument. This can help make your code more readable.
You are not limited to throwing NSException objects. You can throw any Objective-C object as an exception object. The NSException class provides methods that help in exception processing, but you can implement your own if you so desire. You can also subclass NSException to implement specialized types of exceptions, such as file-system exceptions or communications exceptions.
Last updated: 2010-07-13