On Jan 14, 2013, at 4:45 PM, Charles Srstka <[email protected]> wrote:

> On Jan 14, 2013, at 2:38 PM, Kyle Sluder <[email protected]> wrote:
> 
>> Given that Gordon's explicit use case involves one part of his app
>> setting up timers that point at objects in other parts of his app that
>> know nothing of the timers' existence, this sounds like a fragility
>> nightmare.
>> 
>> The NSTimer ship has sailed.
> 
> I don't really see it. All you'd need would be a special initializer or 
> convenience constructor, like +[NSMapTable strongToWeakObjectsMapTable]. Make 
> versions of the +timerWithTimeInterval:etc:etc: classes which would cause the 
> created NSTimer to weakly retain its target, and it'd just work. 


I'm still holding out hope for @doWhatIWant. Stop being so lazy, Apple.

Preston
_______________________________________________

Cocoa-dev mailing list ([email protected])

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 [email protected]

Reply via email to