Re: Could somebody please fix NSTimer?
Re: Could somebody please fix NSTimer?
- Subject: Re: Could somebody please fix NSTimer?
- From: Laurent Daudelin <email@hidden>
- Date: Mon, 14 Jan 2013 16:14:33 -0800
On Jan 14, 2013, at 16:03, William Sumner <email@hidden> wrote:
> On Jan 14, 2013, at 4:45 PM, Charles Srstka <email@hidden> wrote:
>
>> On Jan 14, 2013, at 2:38 PM, Kyle Sluder <email@hidden> 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.
I dont' think Apple engineers are lazy. They are probably extremely busy and have to prioritize. Of course, they could hire more people but throwing more people at a project is not always a guarantee of more work done...
-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin http://www.nemesys-soft.com/
Logiciels Nemesys Software email@hidden
_______________________________________________
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