Posing in Objective-C

Posing enables a subclass to assume the identity of its superclass at runtime. Once posing occurs:

• The original class is replaced globally
• All messages to the original class are redirected to the posing class
• Existing instances behave as instances of the posing class

This was historically used to:

• Intercept and customize behavior
• Extend or fix system classes
• Aid debugging and testing

---

• Only a subclass can pose as its superclass
• Posing affects the entire program
• The original class becomes unavailable
• Must occur before the original class is used
• Unsafe and hard to debug (reason for deprecation)

---

Many examples online confuse class posing with object-level class swapping.

❌ Not Posing:

Using object_setClass(obj, NewClass)
This only changes the class of a single object instance, not the class itself.

✅ True Posing (Legacy):

Using +poseAsClass:
This replaces the entire class globally.

---

[PosingClass poseAsClass:[OriginalClass class]];

Once executed:

• OriginalClass is replaced everywhere
• All messages to OriginalClass go to PosingClass

---

Original Class

@interface Printer : NSObject
- (void)printMessage;
@end

@implementation Printer
- (void)printMessage {
    NSLog(@"Original Printer");
}
@end

Posing Class

@interface DebugPrinter : Printer
@end

@implementation DebugPrinter
+ (void)load {
    [self poseAsClass:[Printer class]];
}

- (void)printMessage {
    NSLog(@"Debug Printer (Posing)");
}
@end

Usage

Printer *p = [[Printer alloc] init];
[p printMessage];

Output

Debug Printer (Posing)

Even though Printer is instantiated, the runtime routes the call to DebugPrinter.

---

Static Posing (Historical Concept)

• Occurs during program load (+load)
• Fixed for the program’s lifetime
• Requires recompilation to change

Dynamic Runtime Tricks (Not True Posing)

• Using object_setClass
• Affects only specific objects
• Does not replace the class globally
• Often mislabelled as “dynamic posing” (incorrect)

---

Posing caused serious problems:

• Global side effects
• Unpredictable behavior
• Difficult debugging
• Breaks encapsulation
• Unsafe with multithreading
• Incompatible with ARC

Apple deprecated posing in favor of safer alternatives.

---

1. Categories (Most Common)

Add methods without replacing the class.

@interface Printer (Debug)
- (void)debugPrint;
@end

---

2. Method Swizzling (Advanced, Use Carefully)

Swap method implementations at runtime.

method_exchangeImplementations(original, swizzled);

---

3. Subclassing

Override behavior in a controlled, object-oriented way.

---

4. Composition (Best Practice)

Wrap behavior instead of replacing it.

---

If asked about posing:

• Clearly state it is deprecated
• Explain what it does conceptually
• Clarify the difference between class posing and object_setClass
• Mention modern alternatives

This shows strong understanding of the Objective-C runtime.

---

• Posing allows a subclass to completely replace its superclass
• All messages to the original class are redirected
• Extremely powerful but unsafe
• Deprecated and unsupported with ARC
• Replaced by categories, swizzling, subclassing, and composition