From fdd72bc94149c7e279b5c4fd5a040af1886a4c72 Mon Sep 17 00:00:00 2001
From: Raimo Niskanen
Date: Thu, 18 Feb 2016 11:17:42 +0100
Subject: Rename retry -> postpone
---
lib/stdlib/doc/src/gen_statem.xml | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
(limited to 'lib/stdlib/doc')
diff --git a/lib/stdlib/doc/src/gen_statem.xml b/lib/stdlib/doc/src/gen_statem.xml
index 5de1812b41..aeab09615c 100644
--- a/lib/stdlib/doc/src/gen_statem.xml
+++ b/lib/stdlib/doc/src/gen_statem.xml
@@ -369,7 +369,7 @@ erlang:'!' -----> Module:StateName/5
The processing order for a state change is:
- - If the option retry is true
+
- If the option postpone is true
the current event is postponed.
- If the state changes the queue of incoming events
@@ -402,10 +402,10 @@ erlang:'!' -----> Module:StateName/5
and the last value is kept.
- retry
- {retry,Retry}
-
- If Retry =:= true
- or plain retry postpone the current event
+ postpone
+ {postpone,Postpone}
+
- If Postpone =:= true
+ or plain postpone postpone the current event
to be retried after a state change.
This option is ignored when returned from
Module:init/1
@@ -434,9 +434,8 @@ erlang:'!' -----> Module:StateName/5
event counts just like a new in this respect.
If Time =:= infinity or Time =:= 0
no timer is started but for zero time the timeout
- event is enqued as just received after all
- other already received events.
- Also note that it is not possible
+ event is immediately enqueued as the newest received.
+ Also note that it is not possible nor needed
to cancel this timeout using the
state_operation()
--
cgit v1.2.3