• 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: Premature _NSAutoreleaseNoPool() warnings -And more
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Premature _NSAutoreleaseNoPool() warnings -And more


  • Subject: Re: Premature _NSAutoreleaseNoPool() warnings -And more
  • From: email@hidden
  • Date: Wed, 3 Apr 2002 10:43:29 EST

I found that my problem was in instantiating static global variables in
the source file of the class, so that was occuring outside of any
NSAutoreleasePool.
But this leads to another question.

Is it necessary to release (autorelease) objects that are in the main()
function if they are to span the duration of the application? They are going
to be destroyed upon exit of the application anyhow, so is it necessary to
create a NSAutorelease pool for them or release them?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Premature _NSAutoreleaseNoPool() warnings -And more
      • From: Ondra Cada <email@hidden>
  • Prev by Date: [ANN] NibLocalizer
  • Next by Date: about kernel's subcomponents...
  • Previous by thread: [ANN] NibLocalizer
  • Next by thread: Re: Premature _NSAutoreleaseNoPool() warnings -And more
  • Index(es):
    • Date
    • Thread