On Mar 17, 2012, at 7:35 PM, Quincey Morris wrote: > The justification given for leaving them on @property was that the > complication of attributes on @synthesize seemed undesirable, and that > @synthesize is headed the way of the dodo anyway.
The memory management behavior of a property frequently is part of the public interface. For example, if you want to understand your retain cycles then it's important to know which properties are strong and which are weak. Or if you have a mutable string then it's important to know which properties are retaining and which are copying. -- Greg Parker gpar...@apple.com Runtime Wrangler _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
