• 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: Using performSelector: on super
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using performSelector: on super


  • Subject: Re: Using performSelector: on super
  • From: James Bucanek <email@hidden>
  • Date: Tue, 5 Aug 2008 12:18:26 -0700

email@hidden <mailto:email@hidden> wrote (Tuesday, August 5, 2008 5:41 AM +0100):
My superclass (SuperSocket) provides a private method -close.

Others have adiquetly explained the whole 'self' vs. 'super' issue, but this statement still has me stumped and I'm wondering why this even came up.


There is no such thing as a "private" method in Objective-C. The @private, @protected, @public keywords only work on instance variables. So if the super class implements -close, there should never be anything stopping your subclass from simply calling [super close].

--
James Bucanek

_______________________________________________

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


  • Follow-Ups:
    • Re: Using performSelector: on super
      • From: "I. Savant" <email@hidden>
    • Re: Using performSelector: on super
      • From: "Shawn Erickson" <email@hidden>
References: 
 >Using performSelector: on super (From: "email@hidden" <email@hidden>)

  • Prev by Date: Re: How is image drawing rate effected by image resolution and size?
  • Next by Date: ERROR in Xcode 3 Unleashed
  • Previous by thread: Re: Using performSelector: on super
  • Next by thread: Re: Using performSelector: on super
  • Index(es):
    • Date
    • Thread