On Tue, 11 May 2004, Uri Guttman wrote:>> Why would alarm need any special opcode when it is just a timer >> with a delay of [abs_time minus NOW]? >> Let the coder handle that and lose the extra opcodes.
mab> you want to make the latency between getting the abs_time, doing mab> the substract[ion] and actually setting up the time as small as mab> possible
Accuracy of delivery (latency) is silly to worry about in Perl for granularities of more than about .05 seconds or so. Building a very fine grained accurate real-time system in Perl makes little sense to me.
so i usually don't worry about who does the delta calculation and the slight amount of delay it takes.
Never mind the granularity or latency, there are systems where "time of day" can be adjusted to take into account clock drift, while "system elapsed time" is left unaffected. Which you want depends on whether you want to sleep for a specific time, or wake up at a specific time, and it would be nice if Parrot didn't rule out making use of that.
Yeah, this is a good point. Interval and time-of-day timer events will stay separate. (And PMCs rather than ops, but that's a separate thing :)
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
