Skip to main content

release Vs nil — Best Practice


When we assign memory to a class variable, should we release it or set it to nil in dealloc method? What is the best practice?



Source: Tips4allCCNA FINAL EXAM

Comments

  1. Best practice:

    [foo release]; // ensures that memory is released
    foo = nil; // ensures that there is no dangling pointer to released memory


    Other notes:

    When you assign to a property declared to retain,

    // in your .h
    @property (retain) MyObject *foo;

    // in your .m
    self.foo = bar; // bar is retained; whatever foo previously pointed at is released


    it will release what it was previously pointing at and retain the new object being assigned.

    So, you can use:

    self.foo = nil;


    and it will release whatever foo was pointing at. However, if your property was not declared to have retain storage semantics, this will not implicitly release whatever foo was pointing at. Also, as Ryan pointed out, a property can be overridden to have side effects. For this reason, it is best to follow the pattern of always using:

    [foo release];


    To ensure that you don't have a dangling pointer to released memory, you can follow this up with:

    foo = nil;


    If you are not using properties with retain semantics, you need to release whatever was stored in the variable:

    [foo release];




    EDIT: Also see the following answer to another question that explains this:

    iPhone - dealloc - Release vs. nil

    ReplyDelete

Post a Comment

Popular posts from this blog

Why is this Javascript much *slower* than its jQuery equivalent?

I have a HTML list of about 500 items and a "filter" box above it. I started by using jQuery to filter the list when I typed a letter (timing code added later): $('#filter').keyup( function() { var jqStart = (new Date).getTime(); var search = $(this).val().toLowerCase(); var $list = $('ul.ablist > li'); $list.each( function() { if ( $(this).text().toLowerCase().indexOf(search) === -1 ) $(this).hide(); else $(this).show(); } ); console.log('Time: ' + ((new Date).getTime() - jqStart)); } ); However, there was a couple of seconds delay after typing each letter (particularly the first letter). So I thought it may be slightly quicker if I used plain Javascript (I read recently that jQuery's each function is particularly slow). Here's my JS equivalent: document.getElementById('filter').addEventListener( 'keyup', function () { var jsStart = (new Date).getTime()...