• 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: Best design pattern for un-archiving instances of shared resources?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Best design pattern for un-archiving instances of shared resources?


  • Subject: Re: Best design pattern for un-archiving instances of shared resources?
  • From: David Spooner <email@hidden>
  • Date: Sun, 21 Oct 2007 13:45:25 -0600


On 21-Oct-07, at 1:25 AM, Barry Wark wrote:

One last question for the gurus: it appears that awakeAfterUsingCoder should follow the memory management rules of an init method, namely returning a retained object (as opposed to an autoreleased object as you might expect from the standard idiom of methods that do not allocate the object). Can someone confirm this?


The way I understand it is -awakeAfterUsingCoder: is called implicitly after -initWithCoder:, so self already has a retain count of one; if you return a different object, it must also have a retain count of one. Of course if you simply return self, as the default implementation does, then you needn't perform an extra retain...


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


  • Follow-Ups:
    • Re: Best design pattern for un-archiving instances of shared resources?
      • From: email@hidden
References: 
 >Best design pattern for un-archiving instances of shared resources? (From: "Barry Wark" <email@hidden>)
 >Re: Best design pattern for un-archiving instances of shared resources? (From: Uli Kusterer <email@hidden>)
 >Re: Best design pattern for un-archiving instances of shared resources? (From: "Barry Wark" <email@hidden>)

  • Prev by Date: Scroller show/hide not triggered on doc resize
  • Next by Date: Re: AppleScript running under Cocoa - major speed issue - SOLVED
  • Previous by thread: Re: Best design pattern for un-archiving instances of shared resources?
  • Next by thread: Re: Best design pattern for un-archiving instances of shared resources?
  • Index(es):
    • Date
    • Thread