Let's say I have a method called foo. What's the difference between:
[self foo];
and
[self performSelector:@selector(foo)];
Are they the same? The first one seems so much easier, so why would you ever want to use the second one?
-
If you're interested in the internals, you may want to have a look at the objc_msgSend function, which Objective-C uses internally to resolve message callsuser123444555621– user1234445556212010-08-01 09:36:56 +00:00Commented Aug 1, 2010 at 9:36
Add a comment
|
3 Answers
From the docs:
The
performSelector:method is equivalent to sending an aSelector message directly to the receiver. For example, all three of the following messages do the same thing:
id myClone = [anObject copy];
id myClone = [anObject performSelector:@selector(copy)];
id myClone = [anObject performSelector:sel_getUid("copy")];
However, the
performSelector:method allows you to send messages that aren’t determined until runtime. A variable selector can be passed as the argument:
SEL myMethod = findTheAppropriateSelectorForTheCurrentSituation();
[anObject performSelector:myMethod];
1 Comment
theMikeSwan
@selector() is also used when registering as the observer of an object, using NSTimer, using sheets & alerts, and performing a selector after a delay.
Well, say you were getting a SEL from somewhere else, and you just wanted to execute it, you'd use this method.
Otherwise, yeah, you'd usually want to use the first example.
1 Comment
node ninja
Can the first example be used if the selector takes arguments?
The first sends a message to an object and so does the second. In almost all cases, you should use the first. It's quicker and clearer. However, the second has its uses. For instance, you can use it in a situation where you would need to supply a call back.
Another powerful use is in combination with NSSelectorFromString(). You can literally decide what message to use at run time based on a string in a configuration file or from user input (don't forget to validate it!). You can even build selector names using NSString -stringWithFormat: etc. For instance, this parser kit uses the technique to inform the program when parser rules have been matched.
