Re: [Q] Using NSInvocation vs. selector with NSTimer
Re: [Q] Using NSInvocation vs. selector with NSTimer
- Subject: Re: [Q] Using NSInvocation vs. selector with NSTimer
- From: JongAm Park <email@hidden>
- Date: Mon, 18 Oct 2010 08:00:55 -0700
On 10/17/2010 4:11 PM, Joar Wingfors wrote:
On 17 okt 2010, at 15.51, JongAm Park wrote:
Although I know that NSInvocation was added (from Leopard?), I didn't use it much.
NSInvocation predates Mac OS X...
Oh. right. I forgot that.
Is there any benefit in using it? My guess is that an NSInvocation instance is used repeatedly, but using the "selector" based method is not inconvenient for the most of cases.
Is there any other benefit in using the NSInvocation?
NSInvocation is a very flexible class, and can be used for a wide variety of tasks, but it is also (therefore) more cumbersome to setup and use for the simpler things that you mention. It is not often used, so if you don't know that you need it, you probably don't.
j o a r
Well, what I asked actually is about the design philosophy and what the
intention of creating of that was. Your last statement can't fulfill my
curiosity. :)
Thanks anyway to spare your time to answer my question.
--
--
子曰 不而不改 是謂過矣니라
공자께서 말씀하시길, 잘못을 하고도 고치지 않는 것, 그것을 잘못이라 한다.
- 論語< 衛 靈 公>편
JongAm Park
email@hidden
Visit my personal blog at http://jongampark.blogspot.com
Visit my technical blog at http://jongampark.wordpress.com
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden