Jerry Krinock <email@hidden> wrote: on 06/06/29 8:17, Finlay Dobbie at email@hidden wrote:
> NSInvocation is probably even more heavyweight, tbh.
And a real pain! After using NSInvocation a few times, I realized "Why am I
putting myself through this torture?"
So, I don't use it NSInvocation or its side-kick NSMethodSignature anymore.
If I need to invoke a method with non-object arguments, I either rewrite the
method so it has object wrappers around its arguments, or else wrap it in
another method that takes only object arguments, then use a
performSelector:.
My rate of hair loss has decreased, without drugs!
Certain things might be a pain and a little more heavy weight, however what is better to use may not always be the best to develop. If NSInvocation performs better and is more stable, then I don't see why it shouldn't be embraced despite the grunt work. I don't think that it has really been determined if either structure is really better in it's core implementation and it's functionality. I could experiement with each different solutions however, I think it would be better for someone that is more experienced than I to explain that.
It is to my understanding that NSInvocation and performSelectorOnMainThread can be used in the same manner, It's determining scalability and stability that my inexperienced fingers can't tell just yet. -Jerrod Fowkes
---------------------------------
Yahoo! Music Unlimited - Access over 1 million songs.Try it free.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
