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

Re: NSOperationQueue question


  • Subject: Re: NSOperationQueue question
  • From: Greg Guerin <email@hidden>
  • Date: Fri, 7 Aug 2009 15:50:55 -0700

Tim Murison wrote:

                [pool release];
        }
}


With GC, the memory use grows forever, without GC, it doesn't grow at all.

With GC, [pool release] is a no-op. You should use [pool drain].

Quoted from NSAutoreleasePool Class Reference, under the description for -drain:

- - - -
Special Considerations
In a garbage-collected environment, release is a no-op, so unless you do not want to give the collector a hint it is important to use drain in any code that may be compiled for a garbage-collected environment.


- - - -


-- GG

_______________________________________________

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


  • Prev by Date: Re: Intel Mac prefpane error
  • Next by Date: Re: NSOperationQueue question
  • Previous by thread: Re: NSOperationQueue question
  • Next by thread: Intel Mac prefpane error
  • Index(es):
    • Date
    • Thread