aboutsummaryrefslogtreecommitdiffstats
path: root/system/doc/design_principles/statem.xml
diff options
context:
space:
mode:
authorRaimo Niskanen <[email protected]>2016-10-12 17:49:26 +0200
committerRaimo Niskanen <[email protected]>2016-10-13 11:14:35 +0200
commitf4de3f5887be010db178a178e1f20027f3e5d22b (patch)
treeb1aab07d8a54591693f241b1801c6ea5cf4c3b19 /system/doc/design_principles/statem.xml
parent77e175589b0ee3c1a4c94aef3cdcdf54cd84c53c (diff)
downloadotp-f4de3f5887be010db178a178e1f20027f3e5d22b.tar.gz
otp-f4de3f5887be010db178a178e1f20027f3e5d22b.tar.bz2
otp-f4de3f5887be010db178a178e1f20027f3e5d22b.zip
Use parameterized types
Diffstat (limited to 'system/doc/design_principles/statem.xml')
-rw-r--r--system/doc/design_principles/statem.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/system/doc/design_principles/statem.xml b/system/doc/design_principles/statem.xml
index 9a50bef7b1..bece95e6b8 100644
--- a/system/doc/design_principles/statem.xml
+++ b/system/doc/design_principles/statem.xml
@@ -214,7 +214,7 @@ handle_event(EventType, EventContent, State, Data) ->
The <c>gen_statem</c> behavior can regardless of callback mode
automatically
<seealso marker="stdlib:gen_statem#type-state_enter">
- call the state function
+ call the state callback
</seealso>
with special arguments whenever the state changes
so you can write state entry actions
@@ -264,7 +264,7 @@ StateName(EventType, EventContent, Data) ->
These are ordered by returning a list of
<seealso marker="stdlib:gen_statem#type-action">actions</seealso>
in the
- <seealso marker="stdlib:gen_statem#type-state_function_result">return tuple</seealso>
+ <seealso marker="stdlib:gen_statem#type-state_callback_result">return tuple</seealso>
from the
<seealso marker="stdlib:gen_statem#Module:StateName/3">callback function</seealso>.
These state transition actions affect the <c>gen_statem</c>
@@ -1141,7 +1141,7 @@ do_unlock() ->
You return a list containing <c>state_enter</c> from your
<seealso marker="stdlib:gen_statem#Module:callback_mode/0"><c>callback_mode/0</c></seealso>
function and the <c>gen_statem</c> engine will call your
- state function once with the arguments
+ state callback once with the arguments
<c>(enter, OldState, ...)</c> whenever the state changes.
Then you just need to handle these event-like calls in all states.
</p>