• 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: Why should we set ivars to nil in dealloc?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why should we set ivars to nil in dealloc?


  • Subject: Re: Why should we set ivars to nil in dealloc?
  • From: Scott Ribe <email@hidden>
  • Date: Wed, 16 Apr 2008 10:56:10 -0500
  • Thread-topic: Why should we set ivars to nil in dealloc?

> For example, how long does the typical app run for with libgmalloc
> hanging out and chewing up pages?

Well, that is actually one reason that I've been wanting to go 64-bit ;-)

--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice


_______________________________________________

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

References: 
 >Re: Why should we set ivars to nil in dealloc? (From: Bill Bumgarner <email@hidden>)

  • Prev by Date: Re: NSString and utf16
  • Next by Date: Re: Enabling File Open/Save etc in a non-document-based application
  • Previous by thread: Re: Why should we set ivars to nil in dealloc?
  • Next by thread: showing a list of objects
  • Index(es):
    • Date
    • Thread