On Mar 21, 2008, at 2:54 PM, Randall Meadows wrote:
I'm thinking I have overused "retain" on a multitude of properties
I have created. What's a good rule of thumb for using "retain"
versus "assign"? Things I explicitly allocate get "retain",
whereas objects I get from other objects get "assign"? That
doesn't seem to cover all the bases. What about objects
instantiated via IBOutlet connections? Readonly? Assign?
I'm still interested in knowing this, if anyone's got any tips or
pointers. The ObjC 2.0 doc doesn't really seem to go into much
detail about this.
... because it's a memory management issue.
Properties give you a means to declare/specify the behaviour, it's up
to you to decide how to use the options based on an understanding of
memory management -- see <http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Tasks/MemoryManagementRules.html#//apple_ref/doc/uid/20000994
>.
mmalc
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
