On Jan 31, 2012, at 5:42 PM, Eeyore wrote: > Even if you eventually decide to use weak references (after discovering the > retain/release calls are a drag on performance), making them strong > references now to see if that fixes the behavior can help you diagnose the > problem
FYI, using weak references doesn't necessarily avoid retain/release pairs. At best it returns to you nil when you would have otherwise gotten an object that was invalid instead. -- David Duncan _______________________________________________ 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
