Re: Is MKMapView just kinda messy?
Re: Is MKMapView just kinda messy?
- Subject: Re: Is MKMapView just kinda messy?
- From: Kyle Sluder <email@hidden>
- Date: Sat, 19 Nov 2011 14:13:43 -0800
On Sat, Nov 19, 2011 at 2:06 PM, G S <email@hidden> wrote:
>> "Examples of weak references in Cocoa include, but are not restricted to, table data sources, outline view items, notification observers, and miscellaneous targets and delegates. [. . .] Likewise, when a delegate object is deallocated, you need to remove the delegate link by sending a setDelegate: message with a nil argument to the other object."
>
> Noted, thanks. This seems like an oft-overlooked problem when lots of
> controls have their delegates set in the XIB; there's no easy way to
> look at the code and make sure that there's a delegate-clearing
> statement for each one.
You just need to make it a habit. When you add a delegate connection,
add the setDelegate:nil at the same time.
Soon ARC's zeroing weak references will make this concern a thing of
the past. But for now, you need to internalize it.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden