On Fri, Mar 21, 2008 at 5:54 PM, Randall Meadows <[EMAIL PROTECTED]> 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.
Think about the Objective-C memory management rules. If, when writing your mutator, you would use -retain, use retain. If you would use assignment, use assign. If you would create a copy, use copy. It's really that simple. Primarily, assign is used for delegate relationships (to avoid retain cycles) and primitives. --Kyle Sluder _______________________________________________ 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]
