That's not even what the error message is saying, it's trying to tell you, as you summarized earlier, that the temporary variable you are assigning to and properly releasing is being called out as a leak, it's not complaining about the ivar.
On 12 Sep, 2013, at 6:52 pm, Graham Cox <graham....@bigpond.com> wrote: > > On 12/09/2013, at 12:34 PM, Bill Cheeseman <wjcheese...@gmail.com> wrote: > >> The retain count is still +1 at the point where the error is reported. > > > But shouldn't it take into account that it was assigned to an ivar that is > retained until -dealloc? Or is it trying to tell me that it will leak if the > enclosing object happens to leak? If so, that would mean thousands of false > positives in most code, which doesn't appear to happen. This particular > object is a singleton that is never deallocated explicitly in fact - is that > it? > > --Graham > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org > > This email sent to r...@rols.org _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
