Bringing setTimeout to ECMAScript

Jorge jorge at jorgechamorro.com
Sun Mar 20 07:30:53 PDT 2011


On 20/03/2011, at 14:00, Wes Garland wrote:
> On Sun, Mar 20, 2011 at 6:03 AM, Jorge <jorge at jorgechamorro.com> wrote:
> will eventually fire g() before f() is nodejs: <https://github.com/joyent/node/pull/604>
> I've never seen that in any browser.
> 
> This sounds like a bug in Node's clamping algorithm.

It's not, there's an -unwanted- 1ms clamp, but that's not the problem. It's a limitation of the optimizations in place in the implementation of setTimeout()/setInterval(). To guarantee the correct order would require a less performant implementation.
-- 
Jorge.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20110320/3bc97ef5/attachment.html>


More information about the es-discuss mailing list