• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Unexpected result from -[super respondsToSelector:]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unexpected result from -[super respondsToSelector:]


  • Subject: Re: Unexpected result from -[super respondsToSelector:]
  • From: Jens Alfke <email@hidden>
  • Date: Sat, 16 Feb 2008 08:46:10 -0800


On 15 Feb '08, at 10:03 PM, Jerry Krinock wrote:

But what's more surprising is that -respondsToSelector doesn't work as expected when sent to super.

This does not tell you whether your superclass responds to a selector. It calls the superclass's _implementation_ of -respondsToSelector:. Which is the same as calling [self respondsToSelector:], unless your class overrides -respondsToSelector: itself.


"super" calls are a slippery concept, but this isn't a bug in - respondsToSelector: or an Obj-C issue. People have been getting confused about this in dynamic OO languages all the way back to Smalltalk-72 :)

—Jens_______________________________________________

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


References: 
 >Unexpected result from -[super respondsToSelector:] (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: Strategies to prevent class name clashes
  • Next by Date: Re: CoreData Performance Mystery
  • Previous by thread: Re: Unexpected result from -[super respondsToSelector:]
  • Next by thread: Setting NSTextField inside drawRect:
  • Index(es):
    • Date
    • Thread