summaryrefslogtreecommitdiff
path: root/system
diff options
context:
space:
mode:
authorSverker Eriksson <sverker@erlang.org>2021-05-07 15:35:58 +0200
committerSverker Eriksson <sverker@erlang.org>2021-05-26 19:37:24 +0200
commit21b7ad04ce3a81260d5a0207879b8aca27bae532 (patch)
tree9a95bf6bc2b5b642e56f85ea297094f2671f4ff8 /system
parent5b762b79a4f969f51ec7200c00e15790a149ec6d (diff)
downloaderlang-21b7ad04ce3a81260d5a0207879b8aca27bae532.tar.gz
Clarify the asynchronousness of signal reception
Diffstat (limited to 'system')
-rw-r--r--system/doc/reference_manual/processes.xml8
1 files changed, 8 insertions, 0 deletions
diff --git a/system/doc/reference_manual/processes.xml b/system/doc/reference_manual/processes.xml
index 204cbf36fc..2d724773a1 100644
--- a/system/doc/reference_manual/processes.xml
+++ b/system/doc/reference_manual/processes.xml
@@ -417,6 +417,14 @@ spawn(Module, Name, Args) -> pid()
<section>
<title>Receiving Signals</title>
<p>
+ Signals are received asynchronously and automatically. There is nothing
+ a process must do to handle the reception of signals, or can do to
+ prevent it. In particular, signal reception is <em>not</em> tied to the
+ execution of a
+ <seeguide marker="expressions#receive"><c>receive</c></seeguide>
+ expression, but can happen anywhere in the execution flow of a process.
+ </p>
+ <p>
When a signal is received by a process, some kind of action is
taken. The specific action taken depends on the signal type,
contents of the signal, and the state of the receiving process.