On Fri, Apr 5, 2013 at 11:09 AM, Nicolas Grilly <[email protected]> wrote: > 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."
Yeah, probably, but I don't want to get into a whole big thing about how throws in Erlang or Haskell or Lisp are actually perfectly safe, or can be made safe in Clojure or Scala, or if only JavaScript had typed catches, we could do this or that. Ugh. Boring tedious useless discussions, those are. Node is for running JavaScript, so JavaScript's limitations are Node program limitations. *JavaScript* throws are fundamentally unsafe if they jump over a branch in the execution-flow graph. To the extent that "language X" is like JavaScript, it will be similarly unsafe. (Ruby and Python are both very similar to JavaScript - stateful, imperative, syntaxy, semi-functional, garbage collected.) -- -- 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.
