I am trying to do some runtime programmation on Objective-C. In order to do this I override the resolveClassMethod method.
Unfortunately I come up with some
In your call
NSLog(@"How are you , %@", [Test dynamic]);
the ARC compiler does not know the return type of the method. But ARC needs to know if the method returns an object to add the appropriate retain
/release
calls for managing the lifetime.
Even without ARC you get a compiler warning
class method '+dynamic' not found (return type defaults to 'id')
but the ARC compiler is more strict.
You can call
NSLog(@"How are you , %@", [[Test class] performSelector:@selector(dynamic)]);
because performSelector
returns an id
. For functions returning anything other than an object you can use NSInvocation
.
Alternatively, you can declare the dynamic
method using a Class Extension:
@interface Test (DynamicMethods)
+ (NSString *)dynamic;
@end
ARC has definitely thrown a wrench into some of the fun runtime method resolution machinery. There are still a few options, however. Equally as ugly as the performSelector:
technique you mentioned is an explicit objc_msgSend()
function call. The function needs to be cast with its return and argument types, like so:
(void (*)(id, SEL)objc_msgSend)([Test class], @selector(dynamic)));
(You'll now get a warning about implicit declaration; just declare extern id objc_msgSend(id, SEL, ...);
somewhere.)
A better option is to cast the object to id
when you make the message send (or store it in an id
variable to begin with). The compiler never knows anything about the messages that id
s respond to, so it can't and doesn't complain about sending arbitrary messages. You can cast a class object to id
just as you can an instance.
[(id)Test dynamic];
or
[(id)testInstance anotherDynamicName];