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

Re: Overriding the release mehod


  • Subject: Re: Overriding the release mehod
  • From: Jonathan Hull <email@hidden>
  • Date: Wed, 25 Jan 2017 15:49:40 -0800

One of my favorite things about this list is that the standard response to a question is to ask about the underlying motivation.  It shows that they are prepared to think deeply about your problem and don’t want to just give you a cookie cutter answer.  One of the main signs of an intelligent person in my mind :-)

Thanks,
Jon

> On Jan 25, 2017, at 3:38 PM, Greg Parker <email@hidden> wrote:
>
> What Are You Trying To Do™ is in fact precisely the correct response to your question. Some overrides of -release need to call [super release]. Others do not. It depends on … what they are trying to do.
>
> Overriding release to unregister an observer is almost certainly a bad idea, but yes, such an override ought to call [super release] if the object is expected to be retained and released and deallocated normally.
>
>
> --
> Greg Parker     email@hidden <mailto:email@hidden>     Runtime Wrangler
>
>
>> On Jan 25, 2017, at 8:23 AM, Dave <email@hidden> wrote:
>>
>> I hate it when people as that question! There are some memory leaks in a 3rd party package. It overrides release to unregister an observer but doesn’t call super. If I call super the leaks go away and all is well. I just want to know where is it documented really, I can’t find it searching the docs.
>>
>> Cheers
>> Dave
>>
>>> On 25 Jan 2017, at 15:55, Mike Abdullah <email@hidden> wrote:
>>>
>>> You’re inevitably going to get asked this:
>>> Why on earth are you overriding release? It’s an incredibly niche thing to do, and the answer probably depends a lot on why you’re overriding it.
>>>
>>>> On 25 Jan 2017, at 16:52, Dave <email@hidden> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Does [suoer release] need to be called if you override this method? I’m 99.99999% sure it does, but I can’t find it anywhere it actually says it in black and white.
>>>>
>>>> All the Best
>>>> Dave
>
> _______________________________________________
>
> 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


_______________________________________________

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: Overriding the release mehod
      • From: Sandor Szatmari <email@hidden>
References: 
 >PDF to Word ( docx) Conversion (From: Peter Hudson <email@hidden>)
 >Overriding the release mehod (From: Dave <email@hidden>)
 >Re: Overriding the release mehod (From: Mike Abdullah <email@hidden>)
 >Re: Overriding the release mehod (From: Dave <email@hidden>)
 >Re: Overriding the release mehod (From: Greg Parker <email@hidden>)

  • Prev by Date: Re: Problem using NSView's scrollRect:by:
  • Next by Date: Re: Problem using NSView's scrollRect:by:
  • Previous by thread: Re: Overriding the release mehod
  • Next by thread: Re: Overriding the release mehod
  • Index(es):
    • Date
    • Thread