From: Benjamin Gruenbaum Date: Thu, 25 Jun 2015 06:17:21 +0000 (+0300) Subject: doc: don't recommend domains for error handling X-Git-Tag: v2.3.3~2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=0f09b8db28fcc56295d4346c98d6950fc3a6f86c;p=platform%2Fupstream%2Fnodejs.git doc: don't recommend domains for error handling Remove the suggestion to use domains for exception handling. Add clarity to "unhandledException". Fixes: https://github.com/nodejs/io.js/issues/2055 PR-URL: https://github.com/nodejs/io.js/pull/2056 Reviewed-By: Trev Norris Reviewed-By: Chris Dickinson --- diff --git a/doc/api/process.markdown b/doc/api/process.markdown index ebff3d6..71c7d3c 100644 --- a/doc/api/process.markdown +++ b/doc/api/process.markdown @@ -104,9 +104,6 @@ Example of listening for `uncaughtException`: Note that `uncaughtException` is a very crude mechanism for exception handling. -Don't use it, use [domains](domain.html) instead. If you do use it, restart -your application after every unhandled exception! - Do *not* use it as the io.js equivalent of `On Error Resume Next`. An unhandled exception means your application - and by extension io.js itself - is in an undefined state. Blindly resuming means *anything* could happen. @@ -114,6 +111,11 @@ is in an undefined state. Blindly resuming means *anything* could happen. Think of resuming as pulling the power cord when you are upgrading your system. Nine out of ten times nothing happens - but the 10th time, your system is bust. +`uncaughtException` should be used to perform synchronous cleanup before +shutting down the process. It is not safe to resume normal operation after +`uncaughtException`. If you do use it, restart your application after every +unhandled exception! + You have been warned. ## Event: 'unhandledRejection'