File 0537-misc-grammar-improvements-and-placement.patch of Package erlang

Overview Repositories Revisions Requests Users Attributes Meta

File 0537-misc-grammar-improvements-and-placement.patch of Package erlang (Revision 2d0cd4533106aac34fcd08e582375727)

Currently displaying revision 2d0cd4533106aac34fcd08e582375727 , Show latest

From 80b3329bc6394534aca401a05d57d38209654e74 Mon Sep 17 00:00:00 2001
From: Bryan Paxton <bryan@starbelly.io>
Date: Tue, 13 Sep 2022 17:30:07 -0500
Subject: [PATCH 7/8] misc grammar improvements and placement

---
 system/doc/design_principles/statem.xml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/system/doc/design_principles/statem.xml b/system/doc/design_principles/statem.xml
index 22582ccd28..914a4ccbc8 100644
--- a/system/doc/design_principles/statem.xml
+++ b/system/doc/design_principles/statem.xml
@@ -1915,17 +1915,17 @@ do_unlock() ->
       A catch-all receive should never be used from a <c>gen_statem</c>
       behaviour (or from any <c>gen_*</c> behaviour),
       as the receive statement is within the <c>gen_*</c> engine itself.
-      Using such a receive may result in system messages
-      being discarded which in turn may lead to unexpected behaviour.
-      If a selective receive must be used then great care should be taken to
-      ensure only messages pertinent to the operation are caught.
-      Likewise, long running operations may result in timeouts and the
-      deferment of system messages, which in turn can lead to undesirable behaviour;
-      thus a reasonable timeout for any blocking operation should be used.
       <seeerl marker="stdlib:sys"><c>sys</c></seeerl>
       compatible behaviours must respond to system messages and therefore
       do that in their engine receive loop,
       passing non-system messages to the <em>callback module</em>.
+      Using a catch-all receive may result in system messages
+      being discarded which in turn may lead to unexpected behaviour.
+      If a selective receive must be used then great care should be taken to
+      ensure that only non-system messages which are pertinent to the operation
+      are caught. Likewise, long-running operations may result in timeouts and the
+      deferment of system messages, which in turn can lead to undesirable behaviour;
+      thus, a reasonable timeout for any blocking operation should be used.
     </p>
     <p>
       The
-- 
2.35.3

Places

File 0537-misc-grammar-improvements-and-placement.patch of Package erlang (Revision 2d0cd4533106aac34fcd08e582375727)

Places