• 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: NSCell, copying, and objectValue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSCell, copying, and objectValue


  • Subject: Re: NSCell, copying, and objectValue
  • From: Scott Ribe <email@hidden>
  • Date: Fri, 03 Nov 2006 11:49:57 -0700
  • Thread-topic: NSCell, copying, and objectValue

> Yes, and I'm one of the people who keeps saying don't pay attention to
> retainCount and use ObjectAlloc instead!

If you're trying to track down usage of your own object value class, just
add these methods and set break points on them:

- (id) retain
{ return [super retain]; }

- (void) release
{ [super release]; }

- (id) autorelease
{ return [super autorelease]; }

It's save my sanity a couple of times. (If only by a thin thread...)

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


 _______________________________________________
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: 
 >Re: NSCell, copying, and objectValue (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: column of buttons in NSTableView - a solution?
  • Next by Date: Re: [NewB] printing
  • Previous by thread: Re: NSCell, copying, and objectValue
  • Next by thread: Re: column of buttons in NSTableView - a solution?
  • Index(es):
    • Date
    • Thread