On Friday, April 5, 2013 6:49:31 AM UTC+2, Isaac Schlueter wrote: > I'd argue that throws in Ruby and Python are not safe, either! >
It looks like we agree on the fact that there is nothing fundamentally different in the way `throw` works in JavaScript as a language compared to Python and Ruby. Does it mean that this paragraph of Node.js documentation about domains: "By the very nature of how throw works in JavaScript, there is almost never any way to safely "pick up where you left off", without leaking references, or creating some other sort of undefined brittle state." could be rewritten as is (without "in JavaScript"): "By the very nature of how throw works, there is almost never any way to safely "pick up where you left off", without leaking references, or creating some other sort of undefined brittle state." This is important because the current phrasing makes a beginner like me think there is something specific to Node.js that justifies the strategy "restart process in case of an unexpected error". But in fact it could be a general advice applicable to other technologies as well like Tornado, for example. Correct? -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
