File 3583-Clarify-the-asynchronousness-of-signal-reception.patch of Package erlang

From 21b7ad04ce3a81260d5a0207879b8aca27bae532 Mon Sep 17 00:00:00 2001
From: Sverker Eriksson <sverker@erlang.org>
Date: Fri, 7 May 2021 15:35:58 +0200
Subject: [PATCH 3/3] Clarify the asynchronousness of signal reception

---
 system/doc/reference_manual/processes.xml | 8 ++++++++
 1 file changed, 8 insertions(+)

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
@@ -416,6 +416,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
+	<seealso marker="expressions#receive"><c>receive</c></seealso>
+	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,
-- 
2.26.2

openSUSE Build Service is sponsored by