>while (1); // timer will never fire Thats not what im asking about. There are no while loop, my for loops even use the nextTick. I need to know what kind of delay there is, not if the code is blocking. The longer the delay the more work has been quoted.
Why would someone write a forever loop in js or any other language. > The internal setTimeout/Interval solution is completely ridiculous. Why is anyone even contemplating it? Wring forever loops is "completely ridiculous" your looking at it all wrong. I'm going with something like Jeff Willden wrote, Thanks. On Tuesday, June 5, 2012 11:28:07 PM UTC-4, Ben Noordhuis wrote: > > On Wed, Jun 6, 2012 at 3:21 AM, Tim Dickinson <[email protected]> > wrote: > >>Well sure, but if it's blocked your timeout will never hit. > > > > Never say never. The codes not blocking in that sense. At some point the > > timer will go off. There are no forever loops. > > Sure there are: > > setTimeout(process.exit, 1); > while (1); // timer will never fire > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
