• 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: Memory management/freeing with delegate methods
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory management/freeing with delegate methods


  • Subject: Re: Memory management/freeing with delegate methods
  • From: "Shawn Erickson" <email@hidden>
  • Date: Sat, 28 Apr 2007 15:11:36 -0700

On 4/28/07, Scott Stevenson <email@hidden> wrote:

That is, "self" refers to an instance, "super" refers to a class.

To be pedantic... "super" refers to an object (same object as "self") but message lookup is done in the context of your superclass or to think of it another way... when the metal hits the road [self blah] results in objc_msgSend(self, "blah") while [super blah] results in objc_msgSendSuper(self, "blah").

-Shawn
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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: 
 >Memory management/freeing with delegate methods (From: Paul Borokhov <email@hidden>)
 >Re: Memory management/freeing with delegate methods (From: Scott Stevenson <email@hidden>)
 >Re: Memory management/freeing with delegate methods (From: Paul Borokhov <email@hidden>)
 >Re: Memory management/freeing with delegate methods (From: Scott Stevenson <email@hidden>)

  • Prev by Date: Monitor opened files
  • Next by Date: NSImage data size restriction?
  • Previous by thread: Re: Memory management/freeing with delegate methods
  • Next by thread: Re: Memory management/freeing with delegate methods
  • Index(es):
    • Date
    • Thread