From 953d7184ec95813f40916b40892db3150daf615f Mon Sep 17 00:00:00 2001 From: =?utf8?q?Linus=20Unneb=C3=A4ck?= Date: Thu, 21 Nov 2013 16:39:23 +0100 Subject: [PATCH] doc: clarify child_process error behaviour Clarify that an 'error' event may or may not be followed by an 'exit' event and that it's not safe to make assumptions either way. --- doc/api/child_process.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/api/child_process.markdown b/doc/api/child_process.markdown index d21f7db..40cd183 100644 --- a/doc/api/child_process.markdown +++ b/doc/api/child_process.markdown @@ -36,6 +36,10 @@ Emitted when: 2. The process could not be killed, or 3. Sending a message to the child process failed for whatever reason. +Note that the `exit`-event may or may not fire after an error has occured. If +you are listening on both events to fire a function, remember to guard against +calling your function twice. + See also [`ChildProcess#kill()`](#child_process_child_kill_signal) and [`ChildProcess#send()`](#child_process_child_send_message_sendhandle). -- 2.7.4