Question

There are a couple of things about Objective-C that are confusing to me:

Firstly, in the objective-c guide, it is very clear that each class needs to call the init method of its subclass. It’s a little bit unclear about whether or not a class that inherits directly from NSObject needs to call its init method. Is this the case? And if so, why is that?

Secondly, in the section about NSObject, there’s this warning:

A class that doesn’t need to inherit any special behavior from another class should nevertheless be made a subclass of the NSObject class. Instances of the class must at least have the ability to behave like Objective-C objects at runtime. Inheriting this ability from the NSObject class is much simpler and much more reliable than reinventing it in a new class definition.

Does this mean that I need to specify that all objects inherit from NSObject explicitly? Or is this like Java/Python/C# where all classes are subtypes of NSObject? If not, is there any reason to make a root class other than NSObject?

Answer 1

1) Any time an object is allocated in Objective-C its memory is zeroed out, and must be initialized by a call to init. Subclasses of NSObject may have their own specialized init routines, and at the beginning of such they should call their superclass’ init routine something like so:

self = [super init];

The idea being that all init routines eventually trickle up to NSObject‘s init.

2) You need to be explicit about the inheritance:

@instance myClass : NSObject { /*...*/ } @end

There is no reason to have a root class other than NSObject — a lot of Objective-C relies heavily on this class, so trying to circumvent it will result in you needlessly shooting yourself in the foot.