Understanding Objective-C runtime

Question

This is an excerpt from Objective-C runtime programming guide:

When a new object is created, memory for it is allocated, and its instance variables are initialized. First among the object’s variables is a pointer to its class structure. This pointer, called isa, gives the object access to its class and, through the class, to all the classes it inherits from.

isa is declared in NSObject like this:

Class   isa;

In its turn Class is nothing more than a pointer to the struct

typedef struct objc_class *Class;

And now let's look at this structure:

struct objc_class {
Class isa;

#if !__OBJC2__
Class super_class                                        OBJC2_UNAVAILABLE;
const char *name                                         OBJC2_UNAVAILABLE;
long version                                             OBJC2_UNAVAILABLE;
long info                                                OBJC2_UNAVAILABLE;
long instance_size                                       OBJC2_UNAVAILABLE;
struct objc_ivar_list *ivars                             OBJC2_UNAVAILABLE;
struct objc_method_list **methodLists                    OBJC2_UNAVAILABLE;
struct objc_cache *cache                                 OBJC2_UNAVAILABLE;
struct objc_protocol_list *protocols                     OBJC2_UNAVAILABLE;
#endif

}

We can see that the pointer to the super class (as well as all the rest of the struct's members except another one isa) is unavailable in the latest version of Objective-C.

So my question is how an object can get access to its superclass if super_class pointer is not available? Does it get access to the superclass through this another one isa pointer? But how exactly it happens? How it works? Can anyone explain it?

Where did you find that definition? This header file shows a different one: http://www.opensource.apple.com/source/objc4/objc4-208/runtime/objc-class.h — trojanfoe, Mar 09 '13 at 10:19
@trojanfoe this one is new http://www.opensource.apple.com/source/objc4/objc4-532/runtime/runtime.h — Bryan Chen, Mar 09 '13 at 10:22

Bryan Chen · Accepted Answer · 2013-03-09T10:34:41.540

just checked the source file

objc-class.m

Class class_getSuperclass(Class cls)
{
    return _class_getSuperclass(cls);
}

runtime-new.mm

#define newcls(cls) ((class_t *)cls)

Class 
_class_getSuperclass(Class cls)
{
    return (Class)getSuperclass(newcls(cls));
}

static class_t *
getSuperclass(class_t *cls)
{
    if (!cls) return NULL;
    return cls->superclass;
}

so Class is actually a pointer to class_t

objc-runtime-new.h

typedef struct class_t {
    struct class_t *isa;
    struct class_t *superclass;
    Cache cache;
    IMP *vtable;
    uintptr_t data_NEVER_USE;  // class_rw_t * plus custom rr/alloc flags

    class_rw_t *data() const { 
        return (class_rw_t *)(data_NEVER_USE & ~(uintptr_t)3); 
    }
    void setData(class_rw_t *newData) {
        uintptr_t flags = (uintptr_t)data_NEVER_USE & (uintptr_t)3;
        data_NEVER_USE = (uintptr_t)newData | flags;
    }

    bool hasCustomRR() const {
#if CLASS_FAST_FLAGS_VIA_RW_DATA
        return data_NEVER_USE & (uintptr_t)1;
#else
        return data()->flags & RW_HAS_CUSTOM_RR;
#endif
    }
    void setHasCustomRR(bool inherited = false);

    bool hasCustomAWZ() const {
#if CLASS_FAST_FLAGS_VIA_RW_DATA
        return data_NEVER_USE & (uintptr_t)2;
#else
        return data()->flags & RW_HAS_CUSTOM_AWZ;
#endif
    }
    void setHasCustomAWZ(bool inherited = false);

    bool isRootClass() const {
        return superclass == NULL;
    }
    bool isRootMetaclass() const {
        return isa == this;
    }
} class_t;

and this is the struct that holds everything

anyway, these are internal implementation details and should not be relied on. so do not write code that rely on these because they may broken on next runtime update

hey, but why when i click jump To Definition on Class i get here typedef struct objc_class *Class;? — Andrey Chernukha, Mar 09 '13 at 10:39
@AndreyChernukha I'd imagine it's there to give the compiler something to look at which hiding the actual implementation details. — trojanfoe, Mar 09 '13 at 10:41
One interesting thing I noticed about that objc4 project was the Visual Studio project file as well as the Xcode project files. — trojanfoe, Mar 09 '13 at 10:47
these are implementation details so you cannot see them. and because `Class` is a pointer type so it can point to anything as long as the code uses the pointer knows what is the pointer actually point to. — Bryan Chen, Mar 09 '13 at 10:49
do i understand right that there's no way to find class_t definition through Xcode? — Andrey Chernukha, Mar 09 '13 at 11:00

score 1 · Answer 2 · answered Mar 09 '13 at 10:20

1

dont rely on any internals of the class struct. -- you don't rely on other pals instance variables either! you look for properties

all you can safely do with the runtime is in runtime.h

for getting the superclass e.g.call class_getSuperclass

answered Mar 09 '13 at 10:20

Daij-Djan

49,552
17
113
135

Understanding Objective-C runtime

2 Answers2