Re: Qustion about possibly bad advice in NSView documentation
Re: Qustion about possibly bad advice in NSView documentation
- Subject: Re: Qustion about possibly bad advice in NSView documentation
- From: Alastair Houghton <email@hidden>
- Date: Tue, 25 Sep 2007 20:08:29 +0100
On 25 Sep 2007, at 19:45, Charles Steinman wrote:
--- Alastair Houghton <email@hidden>
wrote:
On 25 Sep 2007, at 16:26, Dominik Pich wrote:
Hi, you verfied this? I was under the impressions
that
performSelector same as NSInvocation transparently
'unwraps'
NSValues........or maybe only NSInvocation!?
I think you're imagining things here. Why would -
performSelector:withObject: ever want to do that?
For a start, you
wouldn't be able to pass an NSValue.
I don't see why not. It could behave the same as KVC,
which works both with scalars and NSValues.
And if you wanted to send an NSValue *object* as an argument of a
message?
Besides, as I said, it's called performSelector:with**Object**:, not
performSelector:withObjectOrMaybeSomethingElseStoredInAnNSValue: :-)
(OK, I'm exaggerating for effect, but the point is that the behaviour
you're describing is not performing a selector with an object, it's
doing something quite different.)
Kind regards,
Alastair.
--
http://alastairs-place.net
_______________________________________________
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