Re: NSStringFromClass versus className ?
Re: NSStringFromClass versus className ?
- Subject: Re: NSStringFromClass versus className ?
- From: Dave Jewell <email@hidden>
- Date: Wed, 20 Feb 2008 16:55:49 +0000
On 20 Feb 2008, at 15:44, glenn andreas wrote:
Probably because className is part of the scripting extensions. As
a result, you won't see it if you browse NSObject.h (so it's not an
obvious idiom), plus everybody knows that AppleScript related stuff
is "icky". Well, maybe not so much the second part, but the first
part is true.
NSStringFromClass also has the advantage that it works for all
classes - not just those that inherit from NSObject. So if I
remember correctly, doing NSStringFromClass on something that is a
proxy will return NSProxy, while className will give you whatever
the proxy is proxying.
Interesting - thanks for that. I was about to disagree with you 'cos
className shows up in the standard documentation for NSObject, but if
you use it in your code, then right-click on it and choose "Jump to
definition", then you will indeed get shunted off to
NSScriptClassDescription.h, which fits with what you said. :-)
Dave
_______________________________________________
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