Bringing setTimeout to ECMAScript

Jorge jorge at
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> wrote:
> will eventually fire g() before f() is nodejs: <>
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list