On Fri, Jan 3, 2014 at 9:44 AM, Jason Shinn <[email protected]> wrote: > Thank you. My main point is that I've been wandering extensively around the > node-verse for the past 6 weeks and this is the first time I've ever seen a > definitive statement that try/catch is actually safe in that (or a similarly > simple) context.
Where did you hear it suggested that try/catch isn't safe? Its perfectly acceptable and recommended to handle errors in node when you know enough about the context to be able to. Node even includes a feature to do so, domains, see the api docs on nodejs.org. Blithely ignoring errors is a bad idea in node, or any other dynamic language where fundamental problems like invalid syntax, non-existent modules during require, attempts to call undefined methods or functions, servers failing to listen because a port is used, etc., are all errors that can be caught. Cheers, Sam -- -- 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.
