In Objective-C, Exceptions can be handled using the standard a common pattern found in most other high-level programming languages. First, you need to place any code that might result in an exception in an (...) block. Then, if an exception is thrown, the corresponding (...) block is executed to handle the problem. The (...) block is called afterwards, regardless of whether or not an exception occurred.

Two distinct types of problems can arise while an iOS or OS X application is running.

In Objective-C programming, error handling is provided with (...) class available in Foundation framework.

(...) is an abstractClass which represents a stream of data. They are used in Archiving and Unarchiving objects. (...) objects are usually used in a method that is being implemented so that the class conforms to the protocol.

The (...) method can be used to see if an object belongs to a class that implements a particular protocol.

In Objective-C, retain counts are the way in which memory is managed in Objective-C

What will be logged? int x = 1; __block int y = 1; void (^test)(void) = ^{ NSLog(@"%i, %i", x, y); }; x = 2; y = 2; test();

What is true regarding messaging?

Which of the following is the fastest?

A class can have two methods with the same name, but with different argument types.

Why should you use an autorelease pool ?