• 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: nested autorelease pools?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: nested autorelease pools?


  • Subject: Re: nested autorelease pools?
  • From: John Stiles <email@hidden>
  • Date: Tue, 1 Nov 2005 14:27:34 -0800

On Nov 1, 2005, at 2:27 PM, Brian O'Brien wrote:

The reason I put the pool creation and release in the init and dealloc methods is because there are other methods of the thread class that allocated objects and I wanted to be sure that those other objects were freed when the thread finalized...

I think putting it in the thread's selector will be sufficient.
If this object can be used on multiple threads, you could be in for a challenge though.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
References: 
 >nested autorelease pools? (From: "Brian O'Brien" <email@hidden>)
 >Re: nested autorelease pools? (From: j o a r <email@hidden>)
 >Re: nested autorelease pools? (From: John Stiles <email@hidden>)
 >Re: nested autorelease pools? (From: j o a r <email@hidden>)
 >Re: nested autorelease pools? (From: John Stiles <email@hidden>)
 >Re: nested autorelease pools? (From: "Brian O'Brien" <email@hidden>)

  • Prev by Date: Re: nested autorelease pools?
  • Next by Date: Re: Objective C++ memory management
  • Previous by thread: Re: nested autorelease pools?
  • Next by thread: Re: nested autorelease pools?
  • Index(es):
    • Date
    • Thread