On Fri, Aug 30, 2013 at 10:49 PM, Peter Skirko <[email protected]> wrote: > Thanks, appreciate the link. Seems like the key part is at the bottom: > > 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... > > So I'm wagering that the catches in Node core as safe b/c they are adhering > to safe rules regarding how they are structured in execution flow.
That's pretty much it. Core is allowed to break all the rules because the people working on it know (or are supposed to know) when it's safe and when it's not. Because of that, it's not a great example of what error handling (or anything really) should look like in a normal application. -- -- 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.
