Re:Objective-C literals for NSDictionary, NSArray, and NSNumber
by natesm on Sunday February 19, 2012 @04:05PM
(#3610409)
Those first two and following aren't equivalent, are they? Wouldn't they compile, respectively, to:
objc_msgSend(self, @selector(bar));
And: objc_msgSend(self, @selector(performSelector:), @selector(bar));
?
Re:Objective-C literals for NSDictionary, NSArray, and NSNumber
by Zev on Sunday February 19, 2012 @05:48PM
(#3610654)
The first two are the same, with a different syntax, yes.
They would both become:
objc_msgSend(self, @selector(bar));
However, your examples are basically explicitly passing a message (1 and 2), vs dynamically building a message to pass (3).For the second to work, the objc_msgCall function would really be:
objc_msgSend(self, @selector(performSelector:), @selector(bar));
(The first example is saying to self to call the selector (method) named 'bar'. The second example is telling self to call the method 'performSelector:' with an argument of 'bar'.)The runtime may or may not be smart enough to optimize this out. It has never been a bottleneck for me to bother looking into it, and I haven't come across anything to indicate one way or the other.
2. Casting the function is optional, but, helps to prevent things like endian differences and your return value getting mangled when using the same code on PPC and Intel. Not too big of a deal anymore.
3. There are actually two other varieties of objc_msgSend, depending on your return type — specifically, floating point calls should use objc_msgSend_fpret and calls that return a struct should use objc_msgSend_stret.
4. I hope I got this cast right, I didn't try to compile it.