On 23/01/2012, at 04:57, Mikeal Rogers wrote: > On Jan 22, 2012, at January 22, 20121:35 PM, Jorge wrote: >> . Not at all. Not only it doesn't clamp to 4ms (which happens to be a good >> thing, IMO), but its timers often fire out of order ! > > node.js does not conform to the 4ms clamp because that would be silly.
Exactly <http://groups.google.com/group/nodejs-dev/msg/788492357732e93e> > It does not fire timers out of order, that I know of. http://groups.google.com/group/nodejs-dev/browse_thread/thread/922a30cf88a1b784 > If you have a case where that is not true then it's a bug in libuv > (setTimeout's event system is in libuv now) that we need to have fixed. The test that's been disabled: https://github.com/joyent/node/blob/master/test/simple/test-next-tick-ordering.js#L50-54 -- Jorge. _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
