How to remember Cocoa memory management:<\/p>\n
Think NARC<\/strong>: “New Alloc Retain Copy”. If you are not doing any of those things, you don’t need to
release<\/code>.<\/p><\/blockquote>\n–Andiih on Stack Overflow<\/a><\/p>\n
Personally, I like to immediately<\/em>
autorelease<\/code> anything I NARC-ed, on the same line. For example:<\/p>\nFoo* pityTheFoo = [[[Foo alloc] init] autorelease];<\/pre>\nAdmittedly, this makes for some ugly, bracey, lines. But I think it’s worth it, because you never<\/em> having to worry about calling
release<\/code> if you also…<\/p>\nUse a
@property<\/code> (or Setter) Instead ofretain<\/code><\/h3>\nIn other words I would write an
init<\/code> method that looked like:<\/p>\n\n- (id) init\n{\n\tself = [super init];\n\tif (self) {\n\t\t_ivar = [[Foo alloc] init];\n\t}\n\treturn self;\n}<\/pre>\nas:<\/p>\n
\n- (id) init\n{\n\tself = [super init];\n\tif (self) {\n\t\tself._ivar = [[[Foo alloc] init] autorelease];\n\t}\n\treturn self;\n}\n<\/pre>\n(Or
[self setIvar:[[[Foo alloc] init] autorelease]];<\/code> if you are one of those folks who hate the dot-syntax.)<\/p>\nIt’s debatable if using acessors in
init<\/code> anddealloc<\/code><\/a> is a good idea. I even left a comment on that post arguing against it. But since then I’ve done a lot of reflection, and in my experience using a@property<\/code> instead of an explicitrelease<\/code>\/= nil<\/code> solves more problems then it causes. So I think it’s the best practice.<\/p>\nEven if you disagree with me on that point, if the only places you explicitly NARC objects are
init<\/code>,dealloc<\/code>, andsetX:<\/code> methods<\/strong> then I think you’re doing the right thing.<\/p>\nCycles!<\/h3>\n
The last piece of the memory-management puzzle are retain cycles<\/a>. By far the best advice I’ve seen on them is Mike Ash’s article<\/a>. Read it.<\/p>\n","protected":false},"excerpt":{"rendered":"
How to remember Cocoa memory management: Think NARC: “New Alloc Retain Copy”. If you are not doing any of those things, you don’t need to release. –Andiih on Stack Overflow Personally, I like to immediately autorelease anything I NARC-ed, on the same line. For example: Foo* pityTheFoo = [[[Foo alloc] init] autorelease]; Admittedly, this makes […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,203,3,5,4,10],"tags":[376,241,224,375],"class_list":["post-601","post","type-post","status-publish","format-standard","hentry","category-cocoa","category-iphone","category-macosx","category-objective-c","category-programming","category-tips","tag-autorelease","tag-best-practices","tag-memory-management","tag-retain"],"_links":{"self":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts\/601","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/comments?post=601"}],"version-history":[{"count":1,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts\/601\/revisions"}],"predecessor-version":[{"id":602,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts\/601\/revisions\/602"}],"wp:attachment":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/media?parent=601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/categories?post=601"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/tags?post=601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}