On 7月19日, 下午9时00分, Yanick <[EMAIL PROTECTED]> wrote: > Well, there may be many reasons to use setTimeout in a chain of > execution. As I understand it, here are some of them :
Thank for your wonderful explaination. Really helpful. And I suspect that whether it is intended for avoiding function stack overflow in the case that too many functions are pushed into stack, but none gets chance of being popped out, since the parent function keeps waiting for the child to finish but the child has invoked another? I wonder whether javascript handles functions like that, so I'm not sure whether my thought is right? If factual, does it easily happen? Will anyone please tell me what's the maximal allowed depth of the stack? I frequently come across with the error "Stack overflow at line 0" (IE6 does, but firefox), I have no idea which stack it meant to. In my app, I've never use setTimeout to invoke a next function, is it the reason why that error occurs? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
