• 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: Solving memory leaks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Solving memory leaks


  • Subject: Re: Solving memory leaks
  • From: Noah Desch <email@hidden>
  • Date: Sat, 27 Mar 2010 19:51:08 -0400



>  but *not* this:

> self.myFields = [[NSMutableArray alloc] init];
>
> That's a memory leak right there. :)


This discussion is confusing me a bit... lets see if I got this right:

If you are *not* using getters and setters but instead have myFields declared as:

@interface MyClass
{
	NSMutableDictionary *myFields;
}

and you use the above line of code, and subsequently release myFields in your dealloc method.... this would *not* be a memory leak, correct?

-Noah_______________________________________________

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

  • Follow-Ups:
    • Re: Solving memory leaks
      • From: Quincey Morris <email@hidden>
References: 
 >Solving memory leaks (From: Michael Davey <email@hidden>)
 >Re: Solving memory leaks (From: Michael Davey <email@hidden>)
 >Re: Solving memory leaks (From: Klaus Backert <email@hidden>)
 >Re: Solving memory leaks (From: Quincey Morris <email@hidden>)

  • Prev by Date: Re: Solving memory leaks
  • Next by Date: Re: Solving memory leaks
  • Previous by thread: Re: Solving memory leaks
  • Next by thread: Re: Solving memory leaks
  • Index(es):
    • Date
    • Thread