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

Re: overloading release


  • Subject: Re: overloading release
  • From: Scott Anguish <email@hidden>
  • Date: Tue, 27 Dec 2005 18:42:57 -0500

you should not do this here, instead do it in the -dealloc method

if you just implement dealloc, everything else release wise takes care of itself.



On Dec 27, 2005, at 6:41 PM, David Alter wrote:

I just wondering if it is a bad idea to over load release. I have an object that on init allocates a NSMutableArray. So I was thinking on release I should make sure I deallocated it. Kind of simulating distructors in C++. Here is a sample of what I'm doing.

- (oneway void)release
{
if ([self retainCount] == 1)
{
[data release];
}

[super release];

}

- (id)init
{
[super init];
data = [[NSMutableArray alloc] init];
return self;
}

_______________________________________________
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
  • Follow-Ups:
    • Re: overloading release
      • From: j o a r <email@hidden>
References: 
 >overloading release (From: David Alter <email@hidden>)

  • Prev by Date: overloading release
  • Next by Date: Re: overloading release
  • Previous by thread: overloading release
  • Next by thread: Re: overloading release
  • Index(es):
    • Date
    • Thread