Event-Driven State Machines


     Erlang/OTP #otp_base_vsn#
-    Welcome to Erlang/OTP, a complete development environment for concurrent programming.
- 
+    
+    Welcome to Erlang/OTP, a complete development environment for concurrent programming.
+    
+
     Some hints that may get you started faster


-- 
cgit v1.2.3


From c46da866eb1a6396ae1d670436dd6d87b4b8e442 Mon Sep 17 00:00:00 2001
From: Mariano Guerra 
Date: Fri, 21 Oct 2016 16:44:28 +0100
Subject: improve applications and modules list styles

---
 system/doc/top/src/erl_html_tools.erl          | 47 +++++---------------
 system/doc/top/src/otp_man_index.erl           | 61 +++++++++++++-------------
 system/doc/top/templates/applications.html.src | 54 ++++++++++++++++-------
 3 files changed, 78 insertions(+), 84 deletions(-)

(limited to 'system/doc')

diff --git a/system/doc/top/src/erl_html_tools.erl b/system/doc/top/src/erl_html_tools.erl
index d55c2e1164..28a0649658 100644
--- a/system/doc/top/src/erl_html_tools.erl
+++ b/system/doc/top/src/erl_html_tools.erl
@@ -387,9 +387,7 @@ subst("#copyright#", _Info, _Group) ->
     "copyright  Copyright © 1991-2004";
 subst("#groups#", Info, _Group) ->
     [
-     "\n",
-     subst_groups(Info),
-     "\n"
+     subst_groups(Info)
     ];
 subst("#applinks#", Info, Group) ->
     subst_applinks(Info, Group);
@@ -476,16 +474,10 @@ subst_unknown_groups([{_Group,Heading,Apps} | Groups], Text0, Left) ->
 
 
 group_table(Heading,Apps) ->
-    [
-     "  \n",
-     "    \n",
-     "      ",Heading,"\n",
-     "    \n",
-     "  \n",
+    ["",Heading,"",
+     "\n",
      subst_apps(Apps),
-     "  \n",
-     "    \n",
-     "  \n"
+     " \n"
     ].
 
 % Count and split the applications in half to get the right sort
@@ -500,17 +492,11 @@ subst_apps([]) ->
 subst_app(App, [{VSN,_Path,Link,Text}]) ->
     [
      "  \n",
-     "    \n",
-     "      \n",
-     "        \n",
-     "          \n",
-     "        \n",
-     "      \n",
+     "    \n",
      "            ",uc(App),"\n",
      "            ",VSN,"\n",
-     "          \n"
      "    \n",
-     "    \n",
+     "    \n",
      Text,"\n",
      "    \n",
      "  \n"
@@ -518,27 +504,14 @@ subst_app(App, [{VSN,_Path,Link,Text}]) ->
 subst_app(App, [{VSN,_Path,Link,Text} | VerInfos]) ->
     [
      "  \n",
-     "    \n",
-     "      \n",
-     "        \n",
-     "          \n",
-     "          \n",
-     "        \n",
-     "      \n",
+     "    \n",
      "            ",uc(App),
-     "  
\n",
+     "\n",
      "            ",VSN,"\n",
-     "          \n",
-     "            \n",
-     "              \n",
-     "                \n",
-     "              \n",
-     "            \n",
+     "                \n",
      subst_vsn(VerInfos),
-     "                \n"
-     "          \n"
      "    \n",
-     "    \n",
+     "    \n",
      Text,"\n",
      "    \n",
      "  \n"
diff --git a/system/doc/top/src/otp_man_index.erl b/system/doc/top/src/otp_man_index.erl
index 12aaba1423..655d7265f7 100644
--- a/system/doc/top/src/otp_man_index.erl
+++ b/system/doc/top/src/otp_man_index.erl
@@ -154,10 +154,10 @@ gen_html(RefPages, OutFile)->
 	    SortedPages = lists:sort(RefPages),
 	    
 	    lists:foreach(fun({_,Module, App, AppDocDir, RefPagePath}) -> 
-				  io:fwrite(Out, "  \n",[]),
-				  io:fwrite(Out, "    ~s\n", 
+				  io:fwrite(Out, "  \n",[]),
+				  io:fwrite(Out, "    ~s\n", 
 					    [RefPagePath, Module]),
-				  io:fwrite(Out, "    ~s\n", 
+				  io:fwrite(Out, "    ~s\n", 
 					    [filename:join(AppDocDir, "index.html"), 
 					     App]),
 				  io:fwrite(Out, "  \n",[])
@@ -175,41 +175,40 @@ gen_html(RefPages, OutFile)->
 html_header() ->
     "\n"
 	"\n"
-	"\n"
-	"\n"
+	"\n"
+	"\n"
 	"  \n"
-	"  Erlang/OTP Manual Page Index\n"
-	"\n"
-	"\n"
-	"\n"
+	"  Erlang/OTP Manual Page Index\n"
+	"\n"
+	"\n"
+	"\n"
 	"\n"
-	"\n"
-	"[Up | Erlang]\n"
-	"
\n"
-	"OTP Reference Page Index
\n"
-	"\n"
-	"\n"
-	"\n"
-	"\n"
-	"\n"
-	"  \n"
-	"\n".
+	"
\n"
+	"\n"
+	"[ Up | Homepage ]\n"
+	"
\n"
+	"OTP Reference Page Index\n"
+	"\n"
+	"\n"
+	"Manual Page Application\n"
+	"\n"
+	"  \n"
+	"\n".
 
 
 
 html_footer(Year) ->
-    "Manual Page Application\n"
-	"\n"
-	"\n"
-	"
\n"
-	"\n"
-	"\n"
+    "\n"
+	"\n"
+	"\n"
+	"
\n"
+	"\n"
+	"\n"
 	"Copyright © 1991-" ++ Year ++ "\n"
 	"\n"
 	"Ericsson AB\n"
-	"\n"
-	"\n"
-	"\n"
-	"\n".
+	"\n"
+	"\n"
+	"\n"
+	"\n".
diff --git a/system/doc/top/templates/applications.html.src b/system/doc/top/templates/applications.html.src
index 1f73c44d69..001234ad32 100644
--- a/system/doc/top/templates/applications.html.src
+++ b/system/doc/top/templates/applications.html.src
@@ -24,31 +24,53 @@ limitations under the License.
   Erlang/OTP #version# Applications
   
 
 
-
-
+
+    Erlang/OTP Applications
 #groups#
-
 
 
-- 
cgit v1.2.3


From 706ad2d5735ee7b17a60251822cdf34d2b5ede8c Mon Sep 17 00:00:00 2001
From: Mariano Guerra 
Date: Sat, 22 Oct 2016 22:51:10 +0100
Subject: applications font-family matches docs

---
 system/doc/top/templates/applications.html.src | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'system/doc')

diff --git a/system/doc/top/templates/applications.html.src b/system/doc/top/templates/applications.html.src
index 001234ad32..7e939ddcd6 100644
--- a/system/doc/top/templates/applications.html.src
+++ b/system/doc/top/templates/applications.html.src
@@ -26,7 +26,7 @@ limitations under the License.
 
 
   
-    
-    Erlang Timers
+    
+    Generic Time-Outs
     
       The previous example of state time-outs only work if
       the state machine stays in the same state during the
@@ -934,13 +950,68 @@ locked(
       You may want to start a timer in one state and respond
       to the time-out in another, maybe cancel the time-out
       without changing states, or perhaps run multiple
-      time-outs in parallel. All this can be accomplished
-      with Erlang Timers:
+      time-outs in parallel. All this can be accomplished with
+      generic time-outs.
+      They may look a little bit like
+      event time-outs
+      but contain a name to allow for any number of them simultaneously
+      and they are not automatically cancelled.
+    
+    
+      Here is how to accomplish the state time-out
+      in the previous example by instead using a generic time-out
+      named open_tm:
+    
+    
+    case Remaining of
+        [Digit] ->
+	    do_unlock(),
+            {next_state, open, Data#{remaining := Code},
+	     [{{timeout,open_tm},10000,lock}]};
+...
+
+open({timeout,open_tm}, lock, Data) ->
+    do_lock(),
+    {next_state,locked,Data};
+open(cast, {button,_}, Data) ->
+    {keep_state,Data};
+...
+    ]]>
+    
+      Just as
+      state time-outs
+      you can restart or cancel a specific generic time-out
+      by setting it to a new time or infinity.
+    
+    
+      Another way to handle a late time-out can be to not cancel it,
+      but to ignore it if it arrives in a state
+      where it is known to be late.
+    
+  
+
+
+
+  
+    
+    Erlang Timers
+    
+      The most versatile way to handle time-outs is to use
+      Erlang Timers; see
       erlang:start_timer3,4.
+      Most time-out tasks can be performed with the
+      time-out features in gen_statem,
+      but an example of one that can not is if you should need
+      the return value from
+      erlang:cancel_timer(Tref), that is; the remaining time of the timer.
     
     
       Here is how to accomplish the state time-out
-      in the previous example by insted using an Erlang Timer:
+      in the previous example by instead using an Erlang Timer:
     
     
     {keep_state_and_data,
-    [{reply,From,length(Code)}]};
+     [{reply,From,length(Code)}]};
 %%
 %% State: locked
 handle_event(
@@ -1636,7 +1707,7 @@ handle_event(
 	    if
 		Digit =:= LockButton ->
 		    {next_state, {locked,LockButton}, Data,
-		     [{reply,From,locked}]);
+		     [{reply,From,locked}]};
 		true ->
 		    {keep_state_and_data,
 		     [postpone]}
@@ -1710,10 +1781,10 @@ handle_event(
   EventType, EventContent,
   {open,LockButton}, Data) ->
     case {EventType, EventContent} of
-	{enter, _OldState} ->
-	    do_unlock(),
-	    {keep_state_and_data,
-	    [{state_timeout,10000,lock},hibernate]};
+        {enter, _OldState} ->
+            do_unlock(),
+            {keep_state_and_data,
+             [{state_timeout,10000,lock},hibernate]};
 ...
     ]]>
     
-- 
cgit v1.2.3


From a75bda102900c4a7ae3184efa8250c46a86f8588 Mon Sep 17 00:00:00 2001
From: Siri Hansen 
Date: Fri, 21 Apr 2017 15:17:31 +0200
Subject: Document that app names and nodes names are restricted to latin-1

---
 system/doc/reference_manual/character_set.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'system/doc')

diff --git a/system/doc/reference_manual/character_set.xml b/system/doc/reference_manual/character_set.xml
index 1129ad63d8..8e41142fb4 100644
--- a/system/doc/reference_manual/character_set.xml
+++ b/system/doc/reference_manual/character_set.xml
@@ -110,7 +110,8 @@
        Guide.
        From Erlang/OTP 20, atoms and function names are also allowed
        to contain Unicode characters outside the ISO-Latin-1 range.
-       Module names are still restricted to the ISO-Latin-1 range.
+       Module names, application names, and node names are still
+       restricted to the ISO-Latin-1 range.
   
   
     Source File Encoding
-- 
cgit v1.2.3


From 6edb6a45d8b2d2993f50176b3324d3fff97fe123 Mon Sep 17 00:00:00 2001
From: Hans Bolinder 
Date: Thu, 9 Mar 2017 10:12:31 +0100
Subject: stdlib: Improve the Erlang shell's handling of references

As of Erlang/OTP 20.0, the type of ETS tables, ets:tid(), is a
reference(). A request was put forward that the Erlang shell should be
able to handle references in its input.

This commit introduces an extended parser in module lib. It can parse
pids, ports, references, and external funs under the condition that
they can be created in the running system. The parser is meant to be
used internally in Erlang/OTP. The alternative, to extend erl_scan and
erl_parse, was deemed inferior as it would require the abstract format
be able to represent pids, ports, references, and funs, which would be
confusing as they are not expressions as such, but data types.
---
 system/doc/efficiency_guide/processes.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'system/doc')

diff --git a/system/doc/efficiency_guide/processes.xml b/system/doc/efficiency_guide/processes.xml
index afa4325d8e..3b64c863ff 100644
--- a/system/doc/efficiency_guide/processes.xml
+++ b/system/doc/efficiency_guide/processes.xml
@@ -4,7 +4,7 @@
 
   
     
-      20012016
+      20012017
       Ericsson AB. All Rights Reserved.
     
     
@@ -222,7 +222,7 @@ kilo_byte(N, Acc) ->
 
        4> T = ets:new(tab, []).
-17
+#Ref<0.1662103692.2407923716.214181>
 5> ets:insert(T, {key,efficiency_guide:kilo_byte()}).
 true
 6> erts_debug:size(element(2, hd(ets:lookup(T, key)))).
-- 
cgit v1.2.3


From c6bdd67b33b70d862e2a2d0f582106f2e930d970 Mon Sep 17 00:00:00 2001
From: Ingela Anderton Andin 
Date: Thu, 6 Apr 2017 16:03:11 +0200
Subject: stdlib: Deprecate gen_fsm

---
 system/doc/design_principles/fsm.xml       | 338 -----------------------------
 system/doc/design_principles/part.xml      |   1 -
 system/doc/design_principles/spec_proc.xml |  86 ++++----
 system/doc/design_principles/sup_princ.xml |   3 +-
 system/doc/design_principles/xmlfiles.mk   |   1 -
 system/doc/reference_manual/modules.xml    |   1 -
 6 files changed, 45 insertions(+), 385 deletions(-)
 delete mode 100644 system/doc/design_principles/fsm.xml

(limited to 'system/doc')

diff --git a/system/doc/design_principles/fsm.xml b/system/doc/design_principles/fsm.xml
deleted file mode 100644
index 4f2b75e6e8..0000000000
--- a/system/doc/design_principles/fsm.xml
+++ /dev/null
@@ -1,338 +0,0 @@
-
-
-
-
-  
-    
-      19972016
-      Ericsson AB. All Rights Reserved.
-    
-    
-      Licensed under the Apache License, Version 2.0 (the "License");
-      you may not use this file except in compliance with the License.
-      You may obtain a copy of the License at
- 
-          http://www.apache.org/licenses/LICENSE-2.0
-
-      Unless required by applicable law or agreed to in writing, software
-      distributed under the License is distributed on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-      See the License for the specific language governing permissions and
-      limitations under the License.
-    
-    
-
-    gen_fsm Behaviour
-    
-    
-    
-    
-    fsm.xml
-  
-  
-    
-      
-	There is a new behaviour
-	gen_statem
-	that is intended to replace gen_fsm for new code.
-	It has the same features and add some really useful.
-	This module will not be removed for the foreseeable future
-	to keep old state machine implementations running.
-      
-    
-  This section is to be read with the gen_fsm(3) manual page
-    in STDLIB, where all interface functions and callback
-    functions are described in detail.
-
-  
-    Finite-State Machines
-    A Finite-State Machine (FSM) can be described as a set of
-      relations of the form:
-    -State(S) x Event(E) -> Actions(A), State(S')
-    These relations are interpreted as meaning:
-    
-      If we are in state S and event E occurs, we
-        are to perform actions A and make a transition to
-        state S'.
-    
-    For an FSM implemented using the gen_fsm behaviour,
-      the state transition rules are written as a number of Erlang
-      functions, which conform to the following convention:
-    -StateName(Event, StateData) ->
-    .. code for actions here ...
-    {next_state, StateName', StateData'}
-  
-
-  
-    Example
-    A door with a code lock can be viewed as an FSM. Initially,
-      the door is locked. Anytime someone presses a button, this
-      generates an event. Depending on what buttons have been pressed
-      before, the sequence so far can be correct, incomplete, or wrong.
-    If it is correct, the door is unlocked for 30 seconds (30,000 ms).
-      If it is incomplete, we wait for another button to be pressed. If
-      it is is wrong, we start all over, waiting for a new button
-      sequence.
-    Implementing the code lock FSM using gen_fsm results in
-      the following callback module:
-    
-    
-    gen_fsm:start_link({local, code_lock}, code_lock, lists:reverse(Code), []).
-
-button(Digit) ->
-    gen_fsm:send_event(code_lock, {button, Digit}).
-
-init(Code) ->
-    {ok, locked, {[], Code}}.
-
-locked({button, Digit}, {SoFar, Code}) ->
-    case [Digit|SoFar] of
-        Code ->
-            do_unlock(),
-            {next_state, open, {[], Code}, 30000};
-        Incomplete when length(Incomplete)
-            {next_state, locked, {Incomplete, Code}};
-        _Wrong ->
-            {next_state, locked, {[], Code}}
-    end.
-
-open(timeout, State) ->
-    do_lock(),
-    {next_state, locked, State}.]]>
-    The code is explained in the next sections.
-  
-
-  
-    Starting gen_fsm
-    In the example in the previous section, the gen_fsm is
-      started by calling code_lock:start_link(Code):
-    
-start_link(Code) ->
-    gen_fsm:start_link({local, code_lock}, code_lock, lists:reverse(Code), []).
-    
-    start_link calls the function gen_fsm:start_link/4,
-    which spawns and links to a new process, a gen_fsm.
-    
-      
-        The first argument, {local, code_lock}, specifies
-          the name. In this case, the gen_fsm is locally
-	  registered as code_lock.
-        If the name is omitted, the gen_fsm is not registered.
-          Instead its pid must be used. The name can also be given
-	  as {global, Name}, in which case the gen_fsm is
-	  registered using global:register_name/2.
-      
-      
-        The second argument, code_lock, is the name of
-          the callback module, that is, the module where the callback
-          functions are located.
-        The interface functions (start_link and button)
-	  are then located in the same module as the callback
-          functions (init, locked, and open). This
-          is normally good programming practice, to have the code
-          corresponding to one process contained in one module.
-      
-      
-        The third argument, Code, is a list of digits that
-	  which is passed reversed to the callback function init.
-	  Here, init
-          gets the correct code for the lock as indata.
-      
-      
-        The fourth argument, [], is a list of options. See
-          the gen_fsm(3) manual page for available options.
-      
-    
-    If name registration succeeds, the new gen_fsm process calls
-      the callback function code_lock:init(Code). This function
-      is expected to return {ok, StateName, StateData}, where
-      StateName is the name of the initial state of the
-      gen_fsm. In this case locked, assuming the door is
-      locked to begin with. StateData is the internal state of
-      the gen_fsm. (For gen_fsm, the internal state is
-      often referred to 'state data' to
-      distinguish it from the state as in states of a state machine.)
-      In this case, the state data is the button sequence so far (empty
-      to begin with) and the correct code of the lock.
-    
-init(Code) ->
-    {ok, locked, {[], Code}}.
-    gen_fsm:start_link is synchronous. It does not return until
-    the gen_fsm has been initialized and is ready to
-      receive notifications.
-    gen_fsm:start_link must be used if the gen_fsm is
-      part of a supervision tree, that is, started by a supervisor. There
-      is another function, gen_fsm:start, to start a standalone
-      gen_fsm, that is, a gen_fsm that is not part of a
-      supervision tree.
-  
-
-  
-    Notifying about Events
-    The function notifying the code lock about a button event is
-      implemented using gen_fsm:send_event/2:
-    
-button(Digit) ->
-    gen_fsm:send_event(code_lock, {button, Digit}).
-    code_lock is the name of the gen_fsm and must
-      agree with the name used to start it.
-      {button, Digit} is the actual event.
-    The event is made into a message and sent to the gen_fsm.
-      When the event is received, the gen_fsm calls
-      StateName(Event, StateData), which is expected to return a
-      tuple {next_state,StateName1,StateData1}.
-      StateName is the name of the current state and
-      StateName1 is the name of the next state to go to.
-      StateData1 is a new value for the state data of
-      the gen_fsm.
-    
-    case [Digit|SoFar] of
-        Code ->
-            do_unlock(),
-            {next_state, open, {[], Code}, 30000};
-        Incomplete when length(Incomplete)
-            {next_state, locked, {Incomplete, Code}};
-        _Wrong ->
-            {next_state, locked, {[], Code}};
-    end.
-
-open(timeout, State) ->
-    do_lock(),
-    {next_state, locked, State}.]]>
-    If the door is locked and a button is pressed, the complete
-      button sequence so far is compared with the correct code for
-      the lock and, depending on the result, the door is either unlocked
-      and the gen_fsm goes to state open, or the door
-      remains in state locked.
-  
-
-  
-    Time-Outs
-    When a correct code has been given, the door is unlocked and
-      the following tuple is returned from locked/2:
-    
-{next_state, open, {[], Code}, 30000};
-    30,000 is a time-out value in milliseconds. After this time,
-      that is, 30 seconds, a time-out occurs. Then,
-      StateName(timeout, StateData) is called. The time-out
-      then occurs when the door has been in state open for 30
-      seconds. After that the door is locked again:
-    
-open(timeout, State) ->
-    do_lock(),
-    {next_state, locked, State}.
-  
-
-  
-    All State Events
-    Sometimes an event can arrive at any state of the gen_fsm.
-      Instead of sending the message with gen_fsm:send_event/2
-      and writing one clause handling the event for each state function,
-      the message can be sent with gen_fsm:send_all_state_event/2
-      and handled with Module:handle_event/3:
-    
--module(code_lock).
-...
--export([stop/0]).
-...
-
-stop() ->
-    gen_fsm:send_all_state_event(code_lock, stop).
-
-...
-
-handle_event(stop, _StateName, StateData) ->
-    {stop, normal, StateData}.
-  
-
-  
-    Stopping
-
-    
-      In a Supervision Tree
-      If the gen_fsm is part of a supervision tree, no stop
-        function is needed. The gen_fsm is automatically
-	terminated by its supervisor. Exactly how this is done is
-	defined by a
-	shutdown strategy
-        set in the supervisor.
-      If it is necessary to clean up before termination, the shutdown
-        strategy must be a time-out value and the gen_fsm must be
-	set to trap exit signals in the init function. When ordered
-        to shutdown, the gen_fsm then calls the callback function
-        terminate(shutdown, StateName, StateData):
-      
-init(Args) ->
-    ...,
-    process_flag(trap_exit, true),
-    ...,
-    {ok, StateName, StateData}.
-
-...
-
-terminate(shutdown, StateName, StateData) ->
-    ..code for cleaning up here..
-    ok.
-    
-
-    
-      Standalone gen_fsm
-      If the gen_fsm is not part of a supervision tree, a stop
-        function can be useful, for example:
-      
-...
--export([stop/0]).
-...
-
-stop() ->
-    gen_fsm:send_all_state_event(code_lock, stop).
-...
-
-handle_event(stop, _StateName, StateData) ->
-    {stop, normal, StateData}.
-
-...
-
-terminate(normal, _StateName, _StateData) ->
-    ok.
-      The callback function handling the stop event returns a
-        tuple, {stop,normal,StateData1}, where normal
-        specifies that it is a normal termination and StateData1
-        is a new value for the state data of the gen_fsm. This
-        causes the gen_fsm to call
-        terminate(normal,StateName,StateData1) and then
-        it terminates gracefully:
-    
-  
-
-  
-    Handling Other Messages
-    If the gen_fsm is to be able to receive other messages
-      than events, the callback function
-      handle_info(Info, StateName, StateData) must be implemented
-      to handle them. Examples of
-      other messages are exit messages, if the gen_fsm is linked to
-      other processes (than the supervisor) and trapping exit signals.
-    
-handle_info({'EXIT', Pid, Reason}, StateName, StateData) ->
-    ..code to handle exits here..
-    {next_state, StateName1, StateData1}.
-    The code_change method must also be implemented.
-    
-code_change(OldVsn, StateName, StateData, Extra) ->
-    ..code to convert state (and more) during code change
-    {ok, NextStateName, NewStateData}
-  
-
-
diff --git a/system/doc/design_principles/part.xml b/system/doc/design_principles/part.xml
index 6495211e04..d52070a674 100644
--- a/system/doc/design_principles/part.xml
+++ b/system/doc/design_principles/part.xml
@@ -30,7 +30,6 @@
   
   
   
-  
   
   
   
diff --git a/system/doc/design_principles/spec_proc.xml b/system/doc/design_principles/spec_proc.xml
index 5b156ac263..d663c5df79 100644
--- a/system/doc/design_principles/spec_proc.xml
+++ b/system/doc/design_principles/spec_proc.xml
@@ -45,61 +45,63 @@
     The sys module has functions for simple debugging of
     processes implemented using behaviours. The code_lock
     example from
-    gen_fsm Behaviour
+    gen_statem Behaviour
     is used to illustrate this:
     -% erl
-Erlang (BEAM) emulator version 5.2.3.6 [hipe] [threads:0]
+Erlang/OTP 20 [DEVELOPMENT] [erts-9.0] [source-5ace45e] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false]
 
-Eshell V5.2.3.6  (abort with ^G)
-1> code_lock:start_link([1,2,3,4]).
-{ok,<0.32.0>}
-2> sys:statistics(code_lock, true).
+Eshell V9.0  (abort with ^G)
+1>  code_lock:start_link([1,2,3,4]).
+Lock
+{ok,<0.63.0>}
+2> sys:statistics(code_lock, true).
 ok
-3> sys:trace(code_lock, true).
+3>  sys:trace(code_lock, true).
 ok
-4> code_lock:button(4).
-*DBG* code_lock got event {button,4} in state closed
+4>  code_lock:button(1).
+*DBG* code_lock receive cast {button,1} in state locked
 ok
-*DBG* code_lock switched to state closed
-5> code_lock:button(3).
-*DBG* code_lock got event {button,3} in state closed
+*DBG* code_lock consume cast {button,1} in state locked
+5>  code_lock:button(2).
+*DBG* code_lock receive cast {button,2} in state locked
 ok
-*DBG* code_lock switched to state closed
-6> code_lock:button(2).
-*DBG* code_lock got event {button,2} in state closed
+*DBG* code_lock consume cast {button,2} in state locked
+6>  code_lock:button(3).
+*DBG* code_lock receive cast {button,3} in state locked
 ok
-*DBG* code_lock switched to state closed
-7> code_lock:button(1).
-*DBG* code_lock got event {button,1} in state closed
+*DBG* code_lock consume cast {button,3} in state locked
+7>  code_lock:button(4).
+*DBG* code_lock receive cast {button,4} in state locked
 ok
-OPEN DOOR
-*DBG* code_lock switched to state open
-*DBG* code_lock got event timeout in state open
-CLOSE DOOR
-*DBG* code_lock switched to state closed
-8> sys:statistics(code_lock, get). 
-{ok,[{start_time,{{2003,6,12},{14,11,40}}},
-     {current_time,{{2003,6,12},{14,12,14}}},
-     {reductions,333},
+Unlock
+*DBG* code_lock consume cast {button,4} in state locked
+*DBG* code_lock receive state_timeout lock in state open
+Lock
+*DBG* code_lock consume state_timeout lock in state open
+8> sys:statistics(code_lock, get).
+{ok,[{start_time,{{2017,4,21},{16,8,7}}},
+     {current_time,{{2017,4,21},{16,9,42}}},
+     {reductions,2973},
      {messages_in,5},
      {messages_out,0}]}
-9> sys:statistics(code_lock, false).
+9> sys:statistics(code_lock, false).
 ok
-10> sys:trace(code_lock, false).     
+10> sys:trace(code_lock, false).
 ok
-11> sys:get_status(code_lock).
-{status,<0.32.0>,
-        {module,gen_fsm},
-        [[{'$ancestors',[<0.30.0>]},
-          {'$initial_call',{gen,init_it,
-                                [gen_fsm,<0.30.0>,<0.30.0>,
-                                 {local,code_lock},
-                                 code_lock,
-                                 [1,2,3,4],
-                                 []]}}],
-         running,<0.30.0>,[],
-         [code_lock,closed,{[],[1,2,3,4]},code_lock,infinity]]}
+11> sys:get_status(code_lock).
+{status,<0.63.0>,
+        {module,gen_statem},
+        [[{'$initial_call',{code_lock,init,1}},
+          {'$ancestors',[<0.61.0>]}],
+         running,<0.61.0>,[],
+         [{header,"Status for state machine code_lock"},
+          {data,[{"Status",running},
+                 {"Parent",<0.61.0>},
+                 {"Logged Events",[]},
+                 {"Postponed",[]}]},
+          {data,[{"State",
+                  {locked,#{code => [1,2,3,4],remaining => [1,2,3,4]}}}]}]]}
+    
   
 
   
diff --git a/system/doc/design_principles/sup_princ.xml b/system/doc/design_principles/sup_princ.xml
index 478d1bf714..4fd210aa48 100644
--- a/system/doc/design_principles/sup_princ.xml
+++ b/system/doc/design_principles/sup_princ.xml
@@ -276,7 +276,6 @@ child_spec() = #{id => child_id(),       % mandatory
 	
 	  supervisor:start_link
 	  gen_server:start_link
-	  gen_fsm:start_link
 	  gen_statem:start_link
 	  gen_event:start_link
 	  A function compliant with these functions. For details,
@@ -341,7 +340,7 @@ child_spec() = #{id => child_id(),       % mandatory
         modules are to be a list with one element
           [Module], where Module is the name of
           the callback module, if the child process is a supervisor,
-          gen_server, gen_fsm or gen_statem.
+          gen_server, gen_statem.
 	  If the child process is a gen_event,
           the value shall be dynamic.
         This information is used by the release handler during
diff --git a/system/doc/design_principles/xmlfiles.mk b/system/doc/design_principles/xmlfiles.mk
index e476255d62..8877e94f39 100644
--- a/system/doc/design_principles/xmlfiles.mk
+++ b/system/doc/design_principles/xmlfiles.mk
@@ -24,7 +24,6 @@ DESIGN_PRINCIPLES_CHAPTER_FILES = \
 	des_princ.xml \
 	distributed_applications.xml \
 	events.xml \
-	fsm.xml \
 	statem.xml \
 	gen_server_concepts.xml \
 	included_applications.xml \
diff --git a/system/doc/reference_manual/modules.xml b/system/doc/reference_manual/modules.xml
index 96968b547e..6fe6680c84 100644
--- a/system/doc/reference_manual/modules.xml
+++ b/system/doc/reference_manual/modules.xml
@@ -143,7 +143,6 @@ fact(0) ->           %  |
         standard behaviours:
 	
 	  gen_server
-	  gen_fsm
 	  gen_statem
 	  gen_event
 	  supervisor
-- 
cgit v1.2.3


From 6fa089792c1e323ded81031da17a379d134ccb0c Mon Sep 17 00:00:00 2001
From: mr c0b 
Date: Tue, 2 May 2017 12:23:00 +1130
Subject: system/doc/reference_manual/: fix a typo

---
 system/doc/reference_manual/data_types.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'system/doc')

diff --git a/system/doc/reference_manual/data_types.xml b/system/doc/reference_manual/data_types.xml
index 107e403903..64e9d54a3c 100644
--- a/system/doc/reference_manual/data_types.xml
+++ b/system/doc/reference_manual/data_types.xml
@@ -452,7 +452,7 @@ hello
 <<"77">>
 16> float_to_binary(7.0).
 <<"7.00000000000000000000e+00">>
-17> binary_to_float(<<"7.000e+00>>").
+17> binary_to_float(<<"7.000e+00">>).
 7.0
   
 
-- 
cgit v1.2.3


From 83e20c62057ebc1d8064bf57b01be560cd244e1d Mon Sep 17 00:00:00 2001
From: Raimo Niskanen 
Date: Thu, 4 May 2017 15:42:21 +0200
Subject: Update copyright year

---
 system/doc/design_principles/part.xml          | 2 +-
 system/doc/design_principles/spec_proc.xml     | 2 +-
 system/doc/design_principles/sup_princ.xml     | 2 +-
 system/doc/design_principles/xmlfiles.mk       | 2 +-
 system/doc/efficiency_guide/binaryhandling.xml | 2 +-
 system/doc/efficiency_guide/commoncaveats.xml  | 2 +-
 system/doc/efficiency_guide/functions.xml      | 2 +-
 system/doc/efficiency_guide/introduction.xml   | 2 +-
 system/doc/efficiency_guide/listhandling.xml   | 2 +-
 system/doc/efficiency_guide/retired_myths.xml  | 2 +-
 system/doc/reference_manual/character_set.xml  | 2 +-
 system/doc/reference_manual/data_types.xml     | 2 +-
 system/doc/reference_manual/errors.xml         | 2 +-
 system/doc/reference_manual/expressions.xml    | 2 +-
 system/doc/reference_manual/introduction.xml   | 2 +-
 system/doc/reference_manual/macros.xml         | 2 +-
 system/doc/reference_manual/modules.xml        | 2 +-
 system/doc/reference_manual/records.xml        | 2 +-
 system/doc/tutorial/c_portdriver.xmlsrc        | 2 +-
 system/doc/tutorial/erl_interface.xmlsrc       | 2 +-
 20 files changed, 20 insertions(+), 20 deletions(-)

(limited to 'system/doc')

diff --git a/system/doc/design_principles/part.xml b/system/doc/design_principles/part.xml
index d52070a674..899c7f2afe 100644
--- a/system/doc/design_principles/part.xml
+++ b/system/doc/design_principles/part.xml
@@ -4,7 +4,7 @@


     
-      19972016
+      19972017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/design_principles/spec_proc.xml b/system/doc/design_principles/spec_proc.xml
index d663c5df79..5f4e7ac685 100644
--- a/system/doc/design_principles/spec_proc.xml
+++ b/system/doc/design_principles/spec_proc.xml
@@ -4,7 +4,7 @@


     
-      19972016
+      19972017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/design_principles/sup_princ.xml b/system/doc/design_principles/sup_princ.xml
index 48b1905e94..06ca44a9f6 100644
--- a/system/doc/design_principles/sup_princ.xml
+++ b/system/doc/design_principles/sup_princ.xml
@@ -4,7 +4,7 @@


     
-      19972016
+      19972017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/design_principles/xmlfiles.mk b/system/doc/design_principles/xmlfiles.mk
index 8877e94f39..fbcaf9c7d9 100644
--- a/system/doc/design_principles/xmlfiles.mk
+++ b/system/doc/design_principles/xmlfiles.mk
@@ -1,7 +1,7 @@
 #
 # %CopyrightBegin%
 # 
-# Copyright Ericsson AB 2009-2016. All Rights Reserved.
+# Copyright Ericsson AB 2009-2017. All Rights Reserved.
 # 
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
diff --git a/system/doc/efficiency_guide/binaryhandling.xml b/system/doc/efficiency_guide/binaryhandling.xml
index 91fd9a7cd9..19f40c9abe 100644
--- a/system/doc/efficiency_guide/binaryhandling.xml
+++ b/system/doc/efficiency_guide/binaryhandling.xml
@@ -5,7 +5,7 @@


     
       2007
-      2016
+      2017
       Ericsson AB, All Rights Reserved
     
     
diff --git a/system/doc/efficiency_guide/commoncaveats.xml b/system/doc/efficiency_guide/commoncaveats.xml
index 94b1c0b222..b41ffc3902 100644
--- a/system/doc/efficiency_guide/commoncaveats.xml
+++ b/system/doc/efficiency_guide/commoncaveats.xml
@@ -4,7 +4,7 @@


     
-      20012016
+      20012017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/efficiency_guide/functions.xml b/system/doc/efficiency_guide/functions.xml
index 1d0f1f68b7..0a8ee7eb34 100644
--- a/system/doc/efficiency_guide/functions.xml
+++ b/system/doc/efficiency_guide/functions.xml
@@ -4,7 +4,7 @@


     
-      20012016
+      20012017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/efficiency_guide/introduction.xml b/system/doc/efficiency_guide/introduction.xml
index b650008ae8..dca2dec95e 100644
--- a/system/doc/efficiency_guide/introduction.xml
+++ b/system/doc/efficiency_guide/introduction.xml
@@ -4,7 +4,7 @@


     
-      20012016
+      20012017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/efficiency_guide/listhandling.xml b/system/doc/efficiency_guide/listhandling.xml
index ec258d7c2a..4f2497359d 100644
--- a/system/doc/efficiency_guide/listhandling.xml
+++ b/system/doc/efficiency_guide/listhandling.xml
@@ -4,7 +4,7 @@


     
-      20012016
+      20012017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/efficiency_guide/retired_myths.xml b/system/doc/efficiency_guide/retired_myths.xml
index 7c6a1262c7..9b914a3b6e 100644
--- a/system/doc/efficiency_guide/retired_myths.xml
+++ b/system/doc/efficiency_guide/retired_myths.xml
@@ -5,7 +5,7 @@


     
       2016
-      2016
+      2017
       Ericsson AB, All Rights Reserved
     
     
diff --git a/system/doc/reference_manual/character_set.xml b/system/doc/reference_manual/character_set.xml
index 8e41142fb4..ef14bf1372 100644
--- a/system/doc/reference_manual/character_set.xml
+++ b/system/doc/reference_manual/character_set.xml
@@ -4,7 +4,7 @@


     
-      20142015
+      20142017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/reference_manual/data_types.xml b/system/doc/reference_manual/data_types.xml
index 107e403903..58734dcd3c 100644
--- a/system/doc/reference_manual/data_types.xml
+++ b/system/doc/reference_manual/data_types.xml
@@ -4,7 +4,7 @@


     
-      20032015
+      20032017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/reference_manual/errors.xml b/system/doc/reference_manual/errors.xml
index 3e2d306561..b16c5da6eb 100644
--- a/system/doc/reference_manual/errors.xml
+++ b/system/doc/reference_manual/errors.xml
@@ -4,7 +4,7 @@


     
-      20032015
+      20032017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/reference_manual/expressions.xml b/system/doc/reference_manual/expressions.xml
index acd1dec901..cf2d5034aa 100644
--- a/system/doc/reference_manual/expressions.xml
+++ b/system/doc/reference_manual/expressions.xml
@@ -4,7 +4,7 @@


     
-      20032016
+      20032017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/reference_manual/introduction.xml b/system/doc/reference_manual/introduction.xml
index c9ce45bbcc..afbdfa7434 100644
--- a/system/doc/reference_manual/introduction.xml
+++ b/system/doc/reference_manual/introduction.xml
@@ -4,7 +4,7 @@


     
-      20032015
+      20032017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/reference_manual/macros.xml b/system/doc/reference_manual/macros.xml
index b6c740dd10..a341307ab7 100644
--- a/system/doc/reference_manual/macros.xml
+++ b/system/doc/reference_manual/macros.xml
@@ -4,7 +4,7 @@


     
-      20032016
+      20032017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/reference_manual/modules.xml b/system/doc/reference_manual/modules.xml
index 6fe6680c84..4a97bfeb7b 100644
--- a/system/doc/reference_manual/modules.xml
+++ b/system/doc/reference_manual/modules.xml
@@ -4,7 +4,7 @@


     
-      20032016
+      20032017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/reference_manual/records.xml b/system/doc/reference_manual/records.xml
index 1eb13b353e..6b26e2c242 100644
--- a/system/doc/reference_manual/records.xml
+++ b/system/doc/reference_manual/records.xml
@@ -4,7 +4,7 @@


     
-      20032015
+      20032017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/tutorial/c_portdriver.xmlsrc b/system/doc/tutorial/c_portdriver.xmlsrc
index da680642b6..c4cf6daa3b 100644
--- a/system/doc/tutorial/c_portdriver.xmlsrc
+++ b/system/doc/tutorial/c_portdriver.xmlsrc
@@ -4,7 +4,7 @@


     
-      20002015
+      20002017
       Ericsson AB. All Rights Reserved.
     
     
diff --git a/system/doc/tutorial/erl_interface.xmlsrc b/system/doc/tutorial/erl_interface.xmlsrc
index ee648c2e88..bf9bd36597 100644
--- a/system/doc/tutorial/erl_interface.xmlsrc
+++ b/system/doc/tutorial/erl_interface.xmlsrc
@@ -4,7 +4,7 @@


     
-      20002015
+      20002017
       Ericsson AB. All Rights Reserved.
     
     
-- 
cgit v1.2.3


From b8d4bd38e343488b5e8539f913650b150cab3ade Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= 
Date: Wed, 17 May 2017 06:24:02 +0200
Subject: Add a link to the Reference Manual from the example page

When doing a Google search for "bit syntax", you could end up
on the programming examples page about bit syntax. The example
page has some reference material, but is far from complete.

Therefore, add a link to the page about bit syntax in the
Reference Manual.

https://bugs.erlang.org/browse/ERL-387
---
 system/doc/programming_examples/bit_syntax.xml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

(limited to 'system/doc')

diff --git a/system/doc/programming_examples/bit_syntax.xml b/system/doc/programming_examples/bit_syntax.xml
index 0af295b7b7..03645bba1b 100644
--- a/system/doc/programming_examples/bit_syntax.xml
+++ b/system/doc/programming_examples/bit_syntax.xml
@@ -32,6 +32,8 @@


     Introduction
+    The complete specification for the bit syntax appears in the
+    Reference Manual.
     In Erlang, a Bin is used for constructing binaries and matching
       binary patterns. A Bin is written with the following syntax:
     
       separated by hyphens.
     
       Type
-      The type can be integer, float, or
-      binary.
+      The most commonly used types are integer, float, and binary.
+      See Bit Syntax Expressions in the Reference Manual for a complete description.
+
       Signedness
       The signedness specification can be either signed
        or unsigned. Notice that signedness only matters for
-- 
cgit v1.2.3


From 96d9a00223aaaf1df7698395be17157a836461ec Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B6rn=20Gustavsson?= 
Date: Wed, 17 May 2017 06:34:00 +0200
Subject: Don't mention R12B

---
 system/doc/programming_examples/bit_syntax.xml | 14 ++++----------
 1 file changed, 4 insertions(+), 10 deletions(-)

(limited to 'system/doc')

diff --git a/system/doc/programming_examples/bit_syntax.xml b/system/doc/programming_examples/bit_syntax.xml
index 03645bba1b..98ad2808cf 100644
--- a/system/doc/programming_examples/bit_syntax.xml
+++ b/system/doc/programming_examples/bit_syntax.xml
@@ -47,7 +47,7 @@ Bin = <>]]>
 <> = Bin ]]>
     Here, Bin is bound and the elements are bound or
       unbound, as in any match.
-    Since Erlang R12B, a Bin does not need to consist of a whole number of bytes.
+    A Bin does not need to consist of a whole number of bytes.
 
     A bitstring is a sequence of zero or more bits, where
     the number of bits does not need to be divisible by 8. If the number
@@ -184,7 +184,7 @@ end.]]>
       The unit size is given as unit:IntegerLiteral.
        The allowed range is 1-256. It is multiplied by
        the Size specifier to give the effective size of
-       the segment. Since Erlang R12B, the unit size specifies the alignment
+       the segment. The unit size specifies the alignment
        for binary segments without size.
     
     
Example:
@@ -322,21 +322,15 @@ foo(<>) ->]]>
 
   
     Appending to a Binary
-    Since Erlang R12B, the following function for creating a binary out of
-    a list of triples of integers is efficient:
+    Appending to a binary in an efficient way can be done as follows:
     
     triples_to_bin(T, <<>>).
 
 triples_to_bin([{X,Y,Z} | T], Acc) ->
-    triples_to_bin(T, <>);   % inefficient before R12B
+    triples_to_bin(T, <>);
 triples_to_bin([], Acc) -> 
     Acc.]]>
-    In previous releases, this function was highly inefficient, because
-    the binary constructed so far (Acc) was copied in each recursion step.
-    That is no longer the case. For more information, see
-    
-    Efficiency Guide.
   
 
 
-- 
cgit v1.2.3


From 51c44f09553b13194ee8346266b0930d1a135590 Mon Sep 17 00:00:00 2001
From: Raimo Niskanen 
Date: Fri, 19 May 2017 11:52:35 +0200
Subject: Fix documentation details

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

(limited to 'system/doc')

diff --git a/system/doc/design_principles/statem.xml b/system/doc/design_principles/statem.xml
index f01615fdcd..7febe31df3 100644
--- a/system/doc/design_principles/statem.xml
+++ b/system/doc/design_principles/statem.xml
@@ -4,7 +4,7 @@


     
-      2016-2017
+      20162017
       Ericsson AB. All Rights Reserved.
     
     
@@ -1582,10 +1582,12 @@ format_status(Opt, [_PDict,State,Data]) ->
       for example, a complex state term like a tuple.

- One reason to use this is when you have - a state item that affects the event handling, - in particular in combination with postponing events. - We complicate the previous example + One reason to use this is when you have a state item + that when changed should cancel the + state time-out, + or one that affects the event handling + in combination with postponing events. + We will complicate the previous example by introducing a configurable lock button (this is the state item in question), which in the open state immediately locks the door, -- cgit v1.2.3 From 30f4fc6963e5793368713897f32afd2172dc1578 Mon Sep 17 00:00:00 2001 From: Lukas Larsson Date: Thu, 18 May 2017 16:11:11 +0200 Subject: otp: Extend secure distribution docs warnings Warnings have been added to the relevant documentation about not using un-secure distributed nodes in exposed environments. --- system/doc/getting_started/conc_prog.xml | 4 ++-- system/doc/reference_manual/distributed.xml | 13 +++++++++++++ 2 files changed, 15 insertions(+), 2 deletions(-) (limited to 'system/doc') diff --git a/system/doc/getting_started/conc_prog.xml b/system/doc/getting_started/conc_prog.xml index f3136898ad..4b19095d95 100644 --- a/system/doc/getting_started/conc_prog.xml +++ b/system/doc/getting_started/conc_prog.xml @@ -355,8 +355,8 @@ pong ! {ping, self()},

Let us rewrite the ping pong program with "ping" and "pong" on different computers. First a few things are needed to set up to get this to work. The distributed Erlang - implementation provides a basic security mechanism to prevent - unauthorized access to an Erlang system on another computer. + implementation provides a very basic authentication mechanism to prevent + unintentional access to an Erlang system on another computer. Erlang systems which talk to each other must have the same magic cookie. The easiest way to achieve this is by having a file called .erlang.cookie in your home diff --git a/system/doc/reference_manual/distributed.xml b/system/doc/reference_manual/distributed.xml index 0a4a323fe9..01d78436c5 100644 --- a/system/doc/reference_manual/distributed.xml +++ b/system/doc/reference_manual/distributed.xml @@ -42,6 +42,19 @@

The distribution mechanism is implemented using TCP/IP sockets. How to implement an alternative carrier is described in the ERTS User's Guide.

+ +

+ Starting a distributed node without also specifying + -proto_dist inet_tls + will expose the node to attacks that may give the attacker + complete access to the node and in extension the cluster. + When using un-secure distributed nodes, make sure that the + network is configured to keep potential attackers out. + See the + Using SSL for Erlang Distribution User's Guide + for details on how to setup a secure distributed node. +

-- cgit v1.2.3 From 43718d3b81d7f3d08e25047e22d579801bbe5044 Mon Sep 17 00:00:00 2001 From: Hans Nilsson Date: Wed, 14 Jun 2017 15:36:21 +0200 Subject: Update copyright year --- system/doc/getting_started/conc_prog.xml | 2 +- system/doc/programming_examples/bit_syntax.xml | 2 +- system/doc/reference_manual/distributed.xml | 2 +- system/doc/top/templates/index.html.src | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) (limited to 'system/doc') diff --git a/system/doc/getting_started/conc_prog.xml b/system/doc/getting_started/conc_prog.xml index 4b19095d95..7936e0d484 100644 --- a/system/doc/getting_started/conc_prog.xml +++ b/system/doc/getting_started/conc_prog.xml @@ -4,7 +4,7 @@

- 20032016 + 20032017 Ericsson AB. All Rights Reserved. diff --git a/system/doc/programming_examples/bit_syntax.xml b/system/doc/programming_examples/bit_syntax.xml index 98ad2808cf..d1dd52c5ab 100644 --- a/system/doc/programming_examples/bit_syntax.xml +++ b/system/doc/programming_examples/bit_syntax.xml @@ -4,7 +4,7 @@

- 20032015 + 20032017 Ericsson AB. All Rights Reserved. diff --git a/system/doc/reference_manual/distributed.xml b/system/doc/reference_manual/distributed.xml index 01d78436c5..b519609717 100644 --- a/system/doc/reference_manual/distributed.xml +++ b/system/doc/reference_manual/distributed.xml @@ -4,7 +4,7 @@

- 20032015 + 20032017 Ericsson AB. All Rights Reserved. diff --git a/system/doc/top/templates/index.html.src b/system/doc/top/templates/index.html.src index b987fb4722..747d19cf7e 100644 --- a/system/doc/top/templates/index.html.src +++ b/system/doc/top/templates/index.html.src @@ -2,7 +2,7 @@

+StateName(enter, _OldState, Data) -> + ... code for state entry here ... + {keep_state, NewData}; +StateName(EventType, EventContent, Data) -> + ... code for actions here ... + {next_state, NewStateName, NewData}.

StateName(enter, _OldState, Data) -> - ... code for state entry here ... + ... code for state entry actions here ... {keep_state, NewData}; StateName(EventType, EventContent, Data) -> ... code for actions here ... @@ -217,7 +215,7 @@ StateName(EventType, EventContent, Data) ->

Depending on how your state machine is specified, this can be a very useful feature, but if you use it - you will have to handle the state entry events in all states. + you will have to handle the state enter call in all states.

-record(rec, {f1 = 42 :: integer(), f2 :: float(), @@ -423,9 +425,10 @@ f2 :: 'undefined' | float(), f3 :: 'undefined' | 'a' | 'b'}).

Erlang/OTP #otp_base_vsn#

Some hints that may get you started faster

Application Groups

Application Groups

Erlang/OTP #otp_base_vsn#

Some hints that may get you started faster

",Heading,"

OTP Reference Page Index

Erlang/OTP Applications