Re: Analyser reports memory leak… where?
Re: Analyser reports memory leak… where?
- Subject: Re: Analyser reports memory leak… where?
- From: Keary Suska <email@hidden>
- Date: Thu, 12 Sep 2013 10:10:16 -0600
On Sep 12, 2013, at 9:52 AM, Graham Cox wrote:
>> At it's core, that's what is really "odd" about the code. It uses a getter that does not comply with the getter convention.
>
> I believe it does. I think your reading of the getter convention may be incorrect. If you can point to explicit documentation that states that the returned object must belong to an autorelease pool, I'll stand corrected, but that would be the first time I've ever heard that in 13 years of Cocoa programming!
I would agree although this Bill's idea might come from a derivation that (IIRC) there is a reasonable expectation that the "gotten" object will persist at least in the current scope, and this can be guaranteed by returning an autoreleased object. But it certainly can't be canon that getters return autoreleased objects, as it is explicitly documented that nonatomic synthesized getters are *not* implemented this way.
Back to the issue at hand, I am curious, is there a property declaration that indicates assign ownership? Also, if you simply set the ivar directly (mEventTypes = [self newEventTypes]), does the warning go away?
HTH,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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