• 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: AutoreleasePool mechanics
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AutoreleasePool mechanics


  • Subject: Re: AutoreleasePool mechanics
  • From: email@hidden (mikevannorsdel)
  • Date: Thu, 20 Dec 2001 07:25:57 -0700

That's about what I figured. What I'm really curious about is the pool
provided by AppKit. Is this pool automatically replaced (cleaned)? If not,
it would seem an application can build a big pile of objects before
termination. The documentation says the AppKit automatically creates and
destroys pools. I wonder when and how often.


On 12/20/01 7:09 AM, "Ondra Cada" <email@hidden> wrote:

> The pool does no magic: it just stores object references, and when it is
> _deallocated_ (!), it releases them all.
>
> Just imagine an NSArray which does not retain objects when inserted: the
> pool does just that (plus a few more tricks like supporting pool hierarchy,
> of course).


  • Follow-Ups:
    • Re: AutoreleasePool mechanics
      • From: Ondra Cada <email@hidden>
    • Re: AutoreleasePool mechanics
      • From: Lance Bland <email@hidden>
References: 
 >Re: AutoreleasePool mechanics (From: Ondra Cada <email@hidden>)

  • Prev by Date: Re: Silly question
  • Next by Date: Re(2): ObjC++ (and a word about Java, too ;-)
  • Previous by thread: Re: AutoreleasePool mechanics
  • Next by thread: Re: AutoreleasePool mechanics
  • Index(es):
    • Date
    • Thread