Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r57648 - in sandbox/msm: boost/msm/back libs/msm/doc libs/msm/doc/index-Dateien
From: christophe.j.henry_at_[hidden]
Date: 2009-11-14 10:36:29

Next message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r57649 - sandbox/stm/branches/vbe/libs/stm/example/tx"
Previous message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r57647 - in sandbox/stm/branches/vbe: boost/stm/tx libs/stm/example/tx"

Author: chenry
Date: 2009-11-14 10:36:28 EST (Sat, 14 Nov 2009)
New Revision: 57648
URL: http://svn.boost.org/trac/boost/changeset/57648

Log:
fixed default-constructor problem
Binary files modified:
   sandbox/msm/libs/msm/doc/index-Dateien/image035.jpg
   sandbox/msm/libs/msm/doc/index-Dateien/image036.jpg
   sandbox/msm/libs/msm/doc/index-Dateien/image037.jpg
   sandbox/msm/libs/msm/doc/index-Dateien/image038.jpg
   sandbox/msm/libs/msm/doc/index-Dateien/image039.jpg
Text files modified:
   sandbox/msm/boost/msm/back/state_machine.hpp | 57 ++
   sandbox/msm/libs/msm/doc/index-Dateien/props0033.xml | 2
   sandbox/msm/libs/msm/doc/index.htm | 816 +++++++++++++++++++++++----------------
   3 files changed, 538 insertions(+), 337 deletions(-)

Modified: sandbox/msm/boost/msm/back/state_machine.hpp
==============================================================================
--- sandbox/msm/boost/msm/back/state_machine.hpp (original)
+++ sandbox/msm/boost/msm/back/state_machine.hpp 2009-11-14 10:36:28 EST (Sat, 14 Nov 2009)
@@ -55,6 +55,10 @@
BOOST_MPL_HAS_XXX_TRAIT_DEF(non_forwarding_flag)
BOOST_MPL_HAS_XXX_TRAIT_DEF(direct_entry)

+#ifndef BOOST_MSM_CONSTRUCTOR_ARG_SIZE
+#define BOOST_MSM_CONSTRUCTOR_ARG_SIZE 5 // default max number of arguments for constructors
+#endif
+
namespace boost { namespace msm { namespace back
{
// event used internally for wrapping a direct entry
@@ -827,6 +831,59 @@
 fill_states(this);
 }

+ // Construct with the default initial states and some default argument(s)
+#ifdef BOOST_MSVC
+
+#define MSM_CONSTRUCTOR_HELPER_EXECUTE_SUB(z, n, unused) ARG ## n t ## n
+#define MSM_CONSTRUCTOR_HELPER_EXECUTE(z, n, unused) \
+ template <BOOST_PP_ENUM_PARAMS(n, class ARG)> \
+ state_machine<Derived,HistoryPolicy \
+ ,WorkaroundVC9 \
+ >(BOOST_PP_ENUM(n, MSM_CONSTRUCTOR_HELPER_EXECUTE_SUB, ~ ) ) \
+ :Derived(BOOST_PP_ENUM_PARAMS(n,t)) \
+ ,m_events_queue() \
+ ,m_deferred_events_queue() \
+ ,m_history() \
+ ,m_event_processing(false) \
+ ,m_is_included(false) \
+ ,m_visitors() \
+ ,m_substate_list() \
+ { \
+ ::boost::mpl::for_each< seq_initial_states, ::boost::msm::back::wrap<mpl::placeholders::_1> > \
+ (init_states(m_states)); \
+ m_history.set_initial_states(m_states); \
+ fill_states(this); \
+ }
+ BOOST_PP_REPEAT_FROM_TO(1,BOOST_PP_ADD(BOOST_MSM_CONSTRUCTOR_ARG_SIZE,1), MSM_CONSTRUCTOR_HELPER_EXECUTE, ~)
+#undef MSM_CONSTRUCTOR_HELPER_EXECUTE
+#undef MSM_CONSTRUCTOR_HELPER_EXECUTE_SUB
+#else
+
+#define MSM_CONSTRUCTOR_HELPER_EXECUTE_SUB(z, n, unused) ARG ## n t ## n
+#define MSM_CONSTRUCTOR_HELPER_EXECUTE(z, n, unused) \
+ template <BOOST_PP_ENUM_PARAMS(n, class ARG)> \
+ state_machine<Derived,HistoryPolicy \
+ >(BOOST_PP_ENUM(n, MSM_CONSTRUCTOR_HELPER_EXECUTE_SUB, ~ ) ) \
+ :Derived(BOOST_PP_ENUM_PARAMS(n,t)) \
+ ,m_events_queue() \
+ ,m_deferred_events_queue() \
+ ,m_history() \
+ ,m_event_processing(false) \
+ ,m_is_included(false) \
+ ,m_visitors() \
+ ,m_substate_list() \
+ { \
+ ::boost::mpl::for_each< seq_initial_states, ::boost::msm::back::wrap<mpl::placeholders::_1> > \
+ (init_states(m_states)); \
+ m_history.set_initial_states(m_states); \
+ fill_states(this); \
+ }
+ BOOST_PP_REPEAT_FROM_TO(1,BOOST_PP_ADD(BOOST_MSM_CONSTRUCTOR_ARG_SIZE,1), MSM_CONSTRUCTOR_HELPER_EXECUTE, ~)
+#undef MSM_CONSTRUCTOR_HELPER_EXECUTE
+#undef MSM_CONSTRUCTOR_HELPER_EXECUTE_SUB
+
+#endif
+
 // assignment operator using the copy policy to decide if non_copyable, shallow or deep copying is necessary
 library_sm& operator= (library_sm const& rhs)
 {

Modified: sandbox/msm/libs/msm/doc/index-Dateien/image035.jpg
==============================================================================
Binary files. No diff available.

Modified: sandbox/msm/libs/msm/doc/index-Dateien/image036.jpg
==============================================================================
Binary files. No diff available.

Modified: sandbox/msm/libs/msm/doc/index-Dateien/image037.jpg
==============================================================================
Binary files. No diff available.

Modified: sandbox/msm/libs/msm/doc/index-Dateien/image038.jpg
==============================================================================
Binary files. No diff available.

Modified: sandbox/msm/libs/msm/doc/index-Dateien/image039.jpg
==============================================================================
Binary files. No diff available.

Modified: sandbox/msm/libs/msm/doc/index-Dateien/props0033.xml
==============================================================================
--- sandbox/msm/libs/msm/doc/index-Dateien/props0033.xml (original)
+++ sandbox/msm/libs/msm/doc/index-Dateien/props0033.xml 2009-11-14 10:36:28 EST (Sat, 14 Nov 2009)
@@ -1,2 +1,2 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<ds:datastoreItem ds:itemID="{510B9391-7F97-4F18-AFC4-2B3C5A63EA09}" xmlns:ds="http://schemas.openxmlformats.org/officeDocument/2006/customXml"><ds:schemaRefs><ds:schemaRef ds:uri="http://schemas.openxmlformats.org/officeDocument/2006/bibliography"/></ds:schemaRefs></ds:datastoreItem>
\ No newline at end of file
+<ds:datastoreItem ds:itemID="{2F692F76-3B14-40AE-8571-9C8DCBB2B21F}" xmlns:ds="http://schemas.openxmlformats.org/officeDocument/2006/customXml"><ds:schemaRefs><ds:schemaRef ds:uri="http://schemas.openxmlformats.org/officeDocument/2006/bibliography"/></ds:schemaRefs></ds:datastoreItem>
\ No newline at end of file

Modified: sandbox/msm/libs/msm/doc/index.htm
==============================================================================
--- sandbox/msm/libs/msm/doc/index.htm (original)
+++ sandbox/msm/libs/msm/doc/index.htm 2009-11-14 10:36:28 EST (Sat, 14 Nov 2009)
@@ -23,15 +23,15 @@
 <o:Author>Christophe</o:Author>
 <o:Template>Normal</o:Template>
 <o:LastAuthor>Christophe</o:LastAuthor>
- <o:Revision>277</o:Revision>
+ <o:Revision>279</o:Revision>
 <o:Created>2009-09-03T20:17:00Z</o:Created>
- <o:LastSaved>2009-11-09T22:04:00Z</o:LastSaved>
+ <o:LastSaved>2009-11-14T15:27:00Z</o:LastSaved>
 <o:Pages>39</o:Pages>
- <o:Words>18815</o:Words>
- <o:Characters>118541</o:Characters>
- <o:Lines>987</o:Lines>
- <o:Paragraphs>274</o:Paragraphs>
- <o:CharactersWithSpaces>137082</o:CharactersWithSpaces>
+ <o:Words>18935</o:Words>
+ <o:Characters>119293</o:Characters>
+ <o:Lines>994</o:Lines>
+ <o:Paragraphs>275</o:Paragraphs>
+ <o:CharactersWithSpaces>137953</o:CharactersWithSpaces>
 <o:Version>12.00</o:Version>
 </o:DocumentProperties>
</xml><![endif]-->
@@ -449,65 +449,73 @@
 panose-1:2 2 6 9 4 2 5 8 3 4;
 mso-font-alt:"\FF2D\FF33 \660E\671D";
 mso-font-charset:128;
- mso-generic-font-family:modern;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:fixed;
- mso-font-signature:-536870145 1791491579 18 0 131231 0;}
+ mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
 {font-family:Batang;
 panose-1:2 3 6 0 0 1 1 1 1 1;
 mso-font-alt:\BC14\D0D5;
 mso-font-charset:129;
- mso-generic-font-family:roman;
- mso-font-pitch:variable;
- mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
+ mso-generic-font-family:auto;
+ mso-font-format:other;
+ mso-font-pitch:fixed;
+ mso-font-signature:1 151388160 16 0 524288 0;}
@font-face
 {font-family:SimSun;
 panose-1:2 1 6 0 3 1 1 1 1 1;
 mso-font-alt:\5B8B\4F53;
 mso-font-charset:134;
 mso-generic-font-family:auto;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:3 680460288 22 0 262145 0;}
+ mso-font-signature:1 135135232 16 0 262144 0;}
@font-face
 {font-family:PMingLiU;
 panose-1:2 2 5 0 0 0 0 0 0 0;
 mso-font-alt:\65B0\7D30\660E\9AD4;
 mso-font-charset:136;
- mso-generic-font-family:roman;
+ mso-generic-font-family:auto;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-1610611969 684719354 22 0 1048577 0;}
+ mso-font-signature:1 134742016 16 0 1048576 0;}
@font-face
 {font-family:"MS Gothic";
 panose-1:2 11 6 9 7 2 5 8 2 4;
 mso-font-alt:"\FF2D\FF33 \30B4\30B7\30C3\30AF";
 mso-font-charset:128;
 mso-generic-font-family:modern;
+ mso-font-format:other;
 mso-font-pitch:fixed;
- mso-font-signature:-536870145 1791491579 18 0 131231 0;}
+ mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
 {font-family:Dotum;
 panose-1:2 11 6 0 0 1 1 1 1 1;
 mso-font-alt:\B3CB\C6C0;
 mso-font-charset:129;
- mso-generic-font-family:swiss;
- mso-font-pitch:variable;
- mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
+ mso-generic-font-family:modern;
+ mso-font-format:other;
+ mso-font-pitch:fixed;
+ mso-font-signature:1 151388160 16 0 524288 0;}
@font-face
 {font-family:SimHei;
 panose-1:2 1 6 9 6 1 1 1 1 1;
 mso-font-alt:\9ED1\4F53;
 mso-font-charset:134;
 mso-generic-font-family:modern;
+ mso-font-format:other;
 mso-font-pitch:fixed;
- mso-font-signature:-2147482945 953122042 22 0 262145 0;}
+ mso-font-signature:1 135135232 16 0 262144 0;}
@font-face
 {font-family:MingLiU;
 panose-1:2 2 5 9 0 0 0 0 0 0;
 mso-font-alt:\7D30\660E\9AD4;
 mso-font-charset:136;
 mso-generic-font-family:modern;
+ mso-font-format:other;
 mso-font-pitch:fixed;
- mso-font-signature:-1610611969 684719354 22 0 1048577 0;}
+ mso-font-signature:1 134742016 16 0 1048576 0;}
@font-face
 {font-family:Mincho;
 panose-1:2 2 6 9 4 3 5 8 3 5;
@@ -522,37 +530,42 @@
 panose-1:2 11 6 0 0 1 1 1 1 1;
 mso-font-alt:\AD74\B9BC;
 mso-font-charset:129;
- mso-generic-font-family:swiss;
- mso-font-pitch:variable;
- mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
+ mso-generic-font-family:roman;
+ mso-font-format:other;
+ mso-font-pitch:fixed;
+ mso-font-signature:1 151388160 16 0 524288 0;}
@font-face
 {font-family:Century;
 panose-1:2 4 6 4 5 5 5 2 3 4;
 mso-font-charset:0;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:647 0 0 0 159 0;}
+ mso-font-signature:3 0 0 0 1 0;}
@font-face
 {font-family:"Angsana New";
 panose-1:2 2 6 3 5 4 5 2 3 4;
- mso-font-charset:0;
+ mso-font-charset:222;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-2130706429 0 0 0 65537 0;}
+ mso-font-signature:16777217 0 0 0 65536 0;}
@font-face
 {font-family:"Cordia New";
 panose-1:2 11 3 4 2 2 2 2 2 4;
- mso-font-charset:0;
- mso-generic-font-family:swiss;
+ mso-font-charset:222;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-2130706429 0 0 0 65537 0;}
+ mso-font-signature:16777217 0 0 0 65536 0;}
@font-face
 {font-family:Mangal;
 panose-1:2 4 5 3 5 2 3 3 2 2;
- mso-font-charset:0;
+ mso-font-charset:1;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:32771 0 0 0 1 0;}
+ mso-font-signature:8192 0 0 0 0 0;}
@font-face
 {font-family:Latha;
 panose-1:2 0 4 0 0 0 0 0 0 0;
@@ -566,29 +579,33 @@
 panose-1:1 10 5 2 5 3 6 3 3 3;
 mso-font-charset:0;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:67110535 0 0 0 159 0;}
+ mso-font-signature:12583555 0 0 0 13 0;}
@font-face
 {font-family:Vrinda;
 panose-1:1 1 6 0 1 1 1 1 1 1;
- mso-font-charset:0;
- mso-generic-font-family:auto;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:65539 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:Raavi;
 panose-1:2 0 5 0 0 0 0 0 0 0;
- mso-font-charset:0;
- mso-generic-font-family:auto;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:131075 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:Shruti;
 panose-1:2 11 6 4 2 2 2 2 2 4;
- mso-font-charset:0;
- mso-generic-font-family:swiss;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:262147 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:Sendnya;
 panose-1:0 0 4 0 0 0 0 0 0 0;
@@ -600,38 +617,43 @@
@font-face
 {font-family:Gautami;
 panose-1:2 0 5 0 0 0 0 0 0 0;
- mso-font-charset:0;
- mso-generic-font-family:auto;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-2145386493 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:Tunga;
 panose-1:0 0 4 0 0 0 0 0 0 0;
- mso-font-charset:0;
- mso-generic-font-family:auto;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:4194307 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:"Estrangelo Edessa";
 panose-1:3 8 6 0 0 0 0 0 0 0;
- mso-font-charset:0;
- mso-generic-font-family:script;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-2147475389 0 128 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:"Cambria Math";
 panose-1:2 4 5 3 5 4 6 3 2 4;
- mso-font-charset:0;
+ mso-font-charset:1;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-1610611985 1107304683 0 0 159 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:"Arial Unicode MS";
 panose-1:2 11 6 4 2 2 2 2 2 4;
- mso-font-charset:128;
- mso-generic-font-family:swiss;
+ mso-font-charset:0;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-134238209 -371195905 63 0 4129279 0;}
+ mso-font-signature:3 0 0 0 1 0;}
@font-face
 {font-family:Cambria;
 panose-1:2 4 5 3 5 4 6 3 2 4;
@@ -1763,7 +1785,8 @@
 font-weight:bold;
 font-style:italic;}
a:link, span.MsoHyperlink
- {mso-style-priority:99;
+ {mso-style-noshow:yes;
+ mso-style-priority:99;
 color:blue;
 text-decoration:underline;
 text-underline:single;}
@@ -3598,6 +3621,38 @@
 mso-level-number-position:left;
 text-indent:-18.0pt;
 font-family:Symbol;}
+@list l36:level2
+ {mso-level-tab-stop:72.0pt;
+ mso-level-number-position:left;
+ text-indent:-18.0pt;}
+@list l36:level3
+ {mso-level-tab-stop:108.0pt;
+ mso-level-number-position:left;
+ text-indent:-18.0pt;}
+@list l36:level4
+ {mso-level-tab-stop:144.0pt;
+ mso-level-number-position:left;
+ text-indent:-18.0pt;}
+@list l36:level5
+ {mso-level-tab-stop:180.0pt;
+ mso-level-number-position:left;
+ text-indent:-18.0pt;}
+@list l36:level6
+ {mso-level-tab-stop:216.0pt;
+ mso-level-number-position:left;
+ text-indent:-18.0pt;}
+@list l36:level7
+ {mso-level-tab-stop:252.0pt;
+ mso-level-number-position:left;
+ text-indent:-18.0pt;}
+@list l36:level8
+ {mso-level-tab-stop:288.0pt;
+ mso-level-number-position:left;
+ text-indent:-18.0pt;}
+@list l36:level9
+ {mso-level-tab-stop:324.0pt;
+ mso-level-number-position:left;
+ text-indent:-18.0pt;}
@list l37
 {mso-list-id:1745571200;
 mso-list-template-ids:-429486050;}
@@ -4944,7 +4999,7 @@
<meta name=CHANGEDBY content=xtoff>
<meta name=CHANGEDBY content=xtoff>
<!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
 <o:idmap v:ext="edit" data="1"/>
@@ -5110,6 +5165,13 @@
lang=EN-US style='mso-ansi-language:EN-US'><a href="#_Processing_events_inside">Processing
events inside from within the front-end</a><o:p></o:p>

+<![if !supportLists]>·       <![endif]><a href="#_State_machine_constructor">State
+machine constructor with arguments</a><o:p></o:p>
+
<a
href="#_Customizing_states">Customizing states</a><o:p></o:p>

@@ -5290,13 +5352,13 @@
lang=EN-US style='font-size:16.0pt;font-family:"Arial","sans-serif";mso-fareast-font-family:
"Times New Roman";mso-ansi-language:EN-US'>Introduction<o:p></o:p></h1>

-Msm is a framework which
-enables you to build a Finite State Machine in a straightforward, descriptive
-and easy-to-use manner. It requires minimal effort to generate a working
-program from an UML state machine diagram. This work was inspired by the state
-machine described in the book of David Abrahams and Aleksey Gurtovoy “C++
-Template Metaprogramming” and adds most of what UML Designers are expecting
-from an UML State Machine framework:<o:p></o:p>
+Msm is a framework which enables
+you to build a Finite State Machine in a straightforward, descriptive and
+easy-to-use manner. It requires minimal effort to generate a working program
+from an UML state machine diagram. This work was inspired by the state machine
+described in the book of David Abrahams and Aleksey Gurtovoy “C++
+Template Metaprogramming” and adds most of what UML Designers are
+expecting from an UML State Machine framework:<o:p></o:p>

<![if !supportLists]>·       
<![endif]>A
-new concept named “flags”. This can be seen as an alternative to Boost.Statechart’s
-state_downcast<o:p></o:p>
+new concept named “flags”. This can be seen as an alternative to
+Boost.Statechart’s state_downcast<o:p></o:p>

<![if !supportLists]><span lang=EN-US style='font-size:
@@ -5440,20 +5502,21 @@
to describe a state machine. Msm now proudly offers as a frontend actions made
of functors instead of actions methods and a new Domain-Specific-Embedded
Language for UML-like description of transition tables named eUML. This
-frontend also allows writing actions and guards directly in the transition
-table or state definition, without the need to define extra functions.<o:p></o:p>
+frontend also allows writing actions and guards directly in the transition table
+or state definition, without the need to define extra functions.<o:p></o:p>

Msm
-was designed with the idea of helping developers build software the Model-Driven-Development
-way. State machines are a very useful tool for MDD, as they allow a graphical
-representation of a dynamic view from a modeled system. Msm aims to provide a
-Model-Driven approach with the reversible and repeatable properties. But the
-help provided by state machines usually stops with the structure definition
-(states, transitions, etc.) and there is little help for actually writing the
-actions, guards and stat actions. Msm now brings MDD further by providing a new
-functional language for the definition of actions and guards directly in the
-transition table. Functional languages have interesting properties, one of
-which is relevant to MDD, the ability to be easily graphically represented.<o:p></o:p>
+was designed with the idea of helping developers build software the
+Model-Driven-Development way. State machines are a very useful tool for MDD, as
+they allow a graphical representation of a dynamic view from a modeled system.
+Msm aims to provide a Model-Driven approach with the reversible and repeatable
+properties. But the help provided by state machines usually stops with the
+structure definition (states, transitions, etc.) and there is little help for
+actually writing the actions, guards and stat actions. Msm now brings MDD
+further by providing a new functional language for the definition of actions
+and guards directly in the transition table. Functional languages have
+interesting properties, one of which is relevant to MDD, the ability to be
+easily graphically represented.<o:p></o:p>

In
a UML diagram, a transition is represented as:<o:p></o:p>
@@ -5724,11 +5787,10 @@

<o:p> </o:p>

-For people working on
-embedded systems, selling Boost.Statechart has got the handicap O (n)
-double-dispatch, the virtual calls and the fact that many of them are coming
-from the C world and thus no fans of big template argument lists or
-forward-declarations.<o:p></o:p>
+For people working on embedded
+systems, selling Boost.Statechart has got the handicap O (n) double-dispatch,
+the virtual calls and the fact that many of them are coming from the C world
+and thus no fans of big template argument lists or forward-declarations.<o:p></o:p>

The declarative interface
of Msm is transparent, and a developer not needing the more complex features is
@@ -5751,9 +5813,9 @@

<o:p> </o:p>

-If you are looking for an
-efficient and straightforward UML-based finite state machine framework, we sincerely
-hope you will enjoy this work!<o:p></o:p>
+If you are looking for an efficient
+and straightforward UML-based finite state machine framework, we sincerely hope
+you will enjoy this work!<o:p></o:p>

<h2><a name="_Founding_example"></a>Founding example<o:p></o:p></h2>
@@ -5772,8 +5834,8 @@
style='mso-ansi-language:EN-US'><o:p></o:p>

<code>p.start(); // activates the init
-state (calls on_entry on the state machine and the first state)</code>p.start(); // activates the
+init state (calls on_entry on the state machine and the first state)</code><o:p></o:p>

@@ -6486,8 +6548,9 @@

SimpleTutorial.cpp<o:p></o:p>

-The previously described transition
-table is an easily-generated view of the following UML State Machine Diagram:<o:p></o:p>
+The previously described
+transition table is an easily-generated view of the following UML State Machine
+Diagram:<o:p></o:p>

<!--[if gte vml 1]><v:shape
 id="Grafik_x0020_15" o:spid="_x0000_i1036" type="#_x0000_t75" alt="SimpleTutorial.jpg"
@@ -6783,8 +6846,8 @@
color:black;mso-ansi-language:EN-US'>No id as an int has to be defined</code><code>,
-which allows reuse of states in other state machines. The ids get generated at
-compile-time. The disadvantage is that it makes debugging harder. See <a
+which allows reuse of states in other state machines. The ids get generated at compile-time.
+The disadvantage is that it makes debugging harder. See <a
href="#_Annex_A_Debugging">Annex A</a> for an explanation of how to find the
generated id. A small helper to get a state array as typeid-generated names is
explained in Annex A and an example is shown
@@ -6846,7 +6909,8 @@
<code>Quite easy, isn't it? You may however
-think the added value is not as great as promised, which leads us to the next tutorials...<o:p></o:p></code>
+think the added value is not as great as promised, which leads us to the next
+tutorials...<o:p></o:p></code>

<o:p> </o:p>
@@ -6861,9 +6925,9 @@

The framework would not be
a very big subset of an UML state machine if it didn't support composite
-states. The UML specification isn't too clear about the difference between composite
-states and sub-state machines, so Msm ignores it for simplicity and defines
-that a composite state is a state machine itself.<o:p></o:p>
+states. The UML specification isn't too clear about the difference between
+composite states and sub-state machines, so Msm ignores it for simplicity and
+defines that a composite state is a state machine itself.<o:p></o:p>

A small example is better
as a long explanation, so, we had player defined as:<o:p></o:p>
@@ -7112,8 +7176,8 @@
<o:p> </o:p>

<h3><a name="_Orthogonal_States_(+Defer"></a>Orthogonal States (+Defer and Terminate
-State)<o:p></o:p></h3>
+"Times New Roman";mso-ansi-language:EN-US'>Orthogonal States (+Defer and
+Terminate State)<o:p></o:p></h3>

<a
href="Orthogonal-deferred.cpp">Orthogonal-deferred.cpp</a><o:p></o:p>
@@ -7183,12 +7247,12 @@
style='font-family:"Courier New";mso-ansi-language:EN-US'>Empty and Open states and get it handled in the first
-state where the event is not to be deferred. It can then be handled or
-rejected. In this example, only when Stopped becomes active will the event be handled as Empty states and get it handled in the
+first state where the event is not to be deferred. It can then be handled or rejected.
+In this example, only when Stopped becomes active will the event be handled as Empty and Open defer the event.<o:p></o:p>
@@ -7236,9 +7300,8 @@
style='font-size:10.0pt;color:#030003;mso-ansi-language:EN-US'>ErrorMode</code><code> : </code><code>public</code><code>
-msm::front::</code><code>terminate_state<></code> msm::front::</code><code>terminate_state<></code><o:p></o:p>

<code></o:p>

-A shallow history reactivates
-the last active state of a submachine when this state machine becomes active
-again. <o:p></o:p>
+A shallow history
+reactivates the last active state of a submachine when this state machine
+becomes active again. <o:p></o:p>

The deep history does the
same recursively, so if this last active state of the submachine was itself a
@@ -7461,9 +7524,9 @@
Flags.cpp<o:p></o:p>

This tutorial is devoted to
-a concept not defined in UML: flags. It has been added into Msm after proving
-itself useful on many occasions. Please, do not be frightened as we are not
-talking about ugly shortcuts made of an improbable collusion of Booleans.<o:p></o:p>
+a concept not defined in UML: flags. It has been added into Msm after proving itself
+useful on many occasions. Please, do not be frightened as we are not talking
+about ugly shortcuts made of an improbable collusion of Booleans.<o:p></o:p>

So what is it and what is
its use?<o:p></o:p>
@@ -7548,8 +7611,8 @@
lang=EN-US style='mso-ansi-language:EN-US'> supports both properties.<o:p></o:p>

Now to check if your player has a
-loaded CD, check if your flag is active in the current state:<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>Now to check if your player has a loaded
+CD, check if your flag is active in the current state:<o:p></o:p>

<code>player</code><code>DirectEntryTutorial</a>.<o:p></o:p>

This tutorial is for expert UML
-designers, and most designers will fortunately never need any of the explained
-concepts, with the possible exception of exit points.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>This tutorial is for expert UML designers,
+and most designers will fortunately never need any of the explained concepts,
+with the possible exception of exit points.<o:p></o:p>

Let us count the ways to enter a
@@ -7788,11 +7851,11 @@
EN-US'>: Entering a submachine through an entry point pseudo state. A pseudo
state is defined as connecting exactly one transition ending on the pseudo
state outside of the submachine to one transition inside the submachine and
-having the pseudo state as source. There are two differences with explicit
-entries. First you have two transitions, meaning two actions (but just one
-guard as UML forbids guard conditions on the inside transition), second you
-have only one transition inside the composite. It is supposed to provide some
-kind of encapsulation.<o:p></o:p>
+having the pseudo state as source. There are two differences with explicit entries.
+First you have two transitions, meaning two actions (but just one guard as UML
+forbids guard conditions on the inside transition), second you have only one
+transition inside the composite. It is supposed to provide some kind of
+encapsulation.<o:p></o:p>

<![if !supportLists]>Explicit entry<o:p></o:p></h4>

First, to define that a state is an
-explicit entry, you have to make it a state and mark it as explicit, giving as
-template parameters the zone id (the zone id starts with 0 and corresponds to
-the first initial state of the First, to define that a state is an explicit
+entry, you have to make it a state and mark it as explicit, giving as template
+parameters the zone id (the zone id starts with 0 and corresponds to the first
+initial state of the initial_state type sequence).<o:p></o:p>

@@ -8094,8 +8157,8 @@

Of course, if these states are found
-in the transition table, which is the common case, this is not necessary. The
-tutorial makes use of this typedef for teaching purposes.<o:p></o:p>
+in the transition table, which is the common case, this is not necessary. The tutorial
+makes use of this typedef for teaching purposes.<o:p></o:p>

<h4 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_Fork_1"></a><o:p></o:p>

And add the
-corresponding transition in Fsm's transition table:<o:p></o:p>
+lang=EN-US style='color:black;mso-ansi-language:EN-US'>And add the corresponding
+transition in Fsm's transition table:<o:p></o:p>

<o:p> </o:p>
@@ -8231,9 +8294,9 @@

And another in the
-SubFsm2_ submachine definition (remember that UML defines an entry point as a
-connection between two transitions), for example this time with an action
-method:<o:p></o:p>
+SubFsm2_ submachine definition (remember that UML defines an entry point as a connection
+between two transitions), for example this time with an action method:<o:p></o:p>

<o:p> </o:p>
@@ -8479,8 +8542,8 @@
According to the UML standard, two
transitions are said to be in conflict if they can both trigger an exit from
-the same state with the same event, meaning if at a certain time and for a
-given event, these two transitions can be triggered.<o:p></o:p>
+the same state with the same event, meaning if at a certain time and for a given
+event, these two transitions can be triggered.<o:p></o:p>

There are two kinds of conflicts,
@@ -8704,8 +8767,8 @@

to get a pointer to the containing state machine. The same applies to
-terminate_state / interrupt_state and entry_pseudo_state / exit_pseudo_state.<o:p></o:p>
+EN-US'>to get a pointer to the containing state machine. The same applies to terminate_state
+/ interrupt_state and entry_pseudo_state / exit_pseudo_state.<o:p></o:p>

<span lang=EN-US style='mso-ansi-language:
@@ -8717,11 +8780,11 @@

It is sometimes necessary to have
-the client code get access to the states' data. After all, the states are
-created once for good and hang around as long as the state machine does so why
-not use it? You simply just need sometimes to get information about any state,
-even inactive ones. An example is if you want to write a coverage tool and know
-how many times a state was visited. How to do it? Again, quite simply:<o:p></o:p>
+the client code get access to the states' data. After all, the states are created
+once for good and hang around as long as the state machine does so why not use
+it? You simply just need sometimes to get information about any state, even
+inactive ones. An example is if you want to write a coverage tool and know how
+many times a state was visited. How to do it? Again, quite simply:<o:p></o:p>

<code>player::Stopped</code><code><code>Of course,
-errors happen. In this case, the state machine is said to be unstable, because
-a transition may have been partially executed. The framework offers a chance to
+errors happen. In this case, the state machine is said to be unstable, because a
+transition may have been partially executed. The framework offers a chance to
set it straight by catching std::exception and calling: </code><o:p></o:p>

@@ -8889,8 +8952,8 @@
style='mso-ansi-font-size:12.0pt;mso-bidi-font-size:12.0pt;color:blue;
mso-ansi-language:EN-US'>const</code><code>: returns true if the state machine is used
-as a composite in another state machine, false otherwise.</code>: returns true if the state machine is
+used as a composite in another state machine, false otherwise.</code><o:p></o:p>

<code>Of these
-jobs, only the last is absolutely necessary to a state machine (its core job),
-the other ones are nice-to-haves which cost CPU time. In many cases, it is not
-so important, but in embedded systems, this can lead to ad-hoc state machine
-implementations.</code><o:p></o:p>
+font-family:"Times New Roman","serif";color:black;mso-ansi-language:EN-US'>Of
+these jobs, only the last is absolutely necessary to a state machine (its core
+job), the other ones are nice-to-haves which cost CPU time. In many cases, it
+is not so important, but in embedded systems, this can lead to ad-hoc state
+machine implementations.</code><o:p></o:p>

<code><span
lang=EN-US style='mso-ansi-font-size:12.0pt;mso-bidi-font-size:12.0pt;
@@ -9052,11 +9116,11 @@
lang=EN-US style='mso-ansi-font-size:12.0pt;mso-bidi-font-size:12.0pt;
font-family:"Times New Roman","serif";color:black;mso-ansi-language:EN-US'>What
is the gain? It will depend on your compiler and target system, so please refer
-to the performance page (where an example is also provided).
-If you use none of these extras, a </code><code>process_event</code><code> </code><code></code><code>process_event</code><code> </code><code>can
execute up to 4 times faster. On a Q6600, an average transition execution lasts
@@ -9110,6 +9174,78 @@
lang=EN-US style='mso-ansi-language:EN-US'>eUML functors have the same
property.<o:p></o:p>

+<o:p> </o:p>
+
+<h3 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
+name="_State_machine_constructor"></a>State machine constructor with arguments<o:p></o:p></h3>
+
+You might want to define a state
+machine with a non-default constructor, which was simple to do with Msm v1.x.
+For example, you might want to write:<o:p></o:p>
+
+<code>struct</code><code> </code><code>player_</code><code> : </code><code>public</code><code> msm::front::</code><code>state_machine_def</code><code><</code><code>player_</code><code>><o:p></o:p></code>
+
+<code>{<o:p></o:p></code>
+
+<code>   player_(int some_value){…}<o:p></o:p></code>
+
+<code>}</code><o:p></o:p>
+
+This is still possible, using the
+back-end as forwarding object:<o:p></o:p>
+
+typedef
+msm::back::state_machine<player_ > player;<o:p></o:p>
+
+player
+p(3);<o:p></o:p>
+
+// do
+something with the state machine<o:p></o:p>
+
+<o:p> </o:p>
+
+Up to the value of the
+BOOST_MSM_CONSTRUCTOR_ARG_SIZE macro (currently 5) arguments. Change this value
+before including any header if you need to change it.<o:p></o:p>
+
<h2 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_Customizing_states"></a><code><span lang=EN-US style='mso-ansi-font-size:
18.0pt;mso-bidi-font-size:16.0pt;font-family:"Times New Roman","serif";
@@ -9119,9 +9255,9 @@
By default, all states derive from msm::default_base_state, which is neither polymorphic nor
-has any other useful purpose than to define a base for all states. The
-following part will describe the customization possibilities offered by Msm.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>, which is neither polymorphic nor has
+any other useful purpose than to define a base for all states. The following
+part will describe the customization possibilities offered by Msm.<o:p></o:p>

<h3 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_User-defined_base_state"></a><code>Important warning: The method visit_current_states takes its parameter by
-value, so if the signature of the accept function is to contain a parameter passed
-by reference, pass this parameter with a boost:ref/cref to avoid undesired
-copies or slicing. So, for example, in the above case, call:<o:p></o:p>
+lang=EN-US style='color:black;mso-ansi-language:EN-US'> takes its parameter by value,
+so if the signature of the accept function is to contain a parameter passed by
+reference, pass this parameter with a boost:ref/cref to avoid undesired copies
+or slicing. So, for example, in the above case, call:<o:p></o:p>

<o:p> </o:p>
@@ -9615,13 +9751,13 @@

This chapter will introduce the new
-features of Msm. This is actually just the beginning of the story; more, much
-more will come!<o:p></o:p>
+features of Msm. This is actually just the beginning of the story; more, much more
+will come!<o:p></o:p>

We will first warm up with a front-end
-based on functors before moving on the eUML, which will provide us with a much
-bigger amount of fun.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>We will first warm up with a
+front-end based on functors before moving on the eUML, which will provide us
+with a much bigger amount of fun.<o:p></o:p>

<h2 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_Frontends"></a>Frontends<o:p></o:p></h2>
@@ -9673,9 +9809,9 @@
lang=EN-US style='font-family:Symbol;mso-fareast-font-family:Symbol;mso-bidi-font-family:
Symbol;mso-ansi-language:EN-US'>·       <![endif]>The action/guard signature is limited
-and does not allow for more variations of parameters (source state, target
-state, current state machine, etc.)<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>The action/guard signature is
+limited and does not allow for more variations of parameters (source state,
+target state, current state machine, etc.)<o:p></o:p>

<p class=MsoListParagraphCxSpLast style='text-indent:-18.0pt;mso-list:l20 level1 lfo25;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>   < Open    , open_close  , Empty   , close_drawer        ,    , close_drawer
+       , none                
>,<o:p></o:p>
@@ -9829,8 +9966,8 @@
style='font-size:10.0pt;font-family:"Courier New";mso-fareast-font-family:"Times New Roman";
color:#030003;mso-ansi-language:EN-US;mso-no-proof:yes'>Row   < Empty   < Empty   , cd_detected
, Stopped , store_cd_info       , ·       <![endif]>“Row” allows reusing
-your functors in other state machines. State machine function pointers cannot
-offer this easily.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>“Row” allows reusing your
+functors in other state machines. State machine function pointers cannot offer
+this easily.<o:p></o:p>

<p class=MsoListParagraphCxSpLast style='text-indent:-18.0pt;mso-list:l14 level1 lfo26;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]><o:p> </o:p>

It is a functor object taking as
-template arguments, the back-end state machine, event, and source and target states.
-<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>It is a functor object taking as template
+arguments, the back-end state machine, event, and source and target states. <o:p></o:p>

Notice how the functor places a new
@@ -10011,8 +10147,8 @@
style='mso-spacerun:yes'> <o:p></o:p>

We can, and why stop here?
-Wouldn’t we like to define guards like: <o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>We can, and why stop here? Wouldn’t
+we like to define guards like: <o:p></o:p>

“<span lang=EN-US
@@ -10059,10 +10195,9 @@
eUML is a
(Boost.)Proto-based compile-time domain specific embedded language. It provides
-grammars which allow the definition of actions/guards directly inside the
-transition table or entry/exit in the state definition. It is defined in the
-namespace msm::front::eumlmsm::front::euml.<o:p></o:p>

<o:p></o:p>

Examples will be
-provided in the next paragraphs. The basic eUML features can be found in:<o:p></o:p>
+lang=EN-US style='color:black;mso-ansi-language:EN-US'>Examples will be provided
+in the next paragraphs. The basic eUML features can be found in:<o:p></o:p>

<p class=MsoNormal style='margin-top:12.0pt;margin-right:36.45pt;margin-bottom:
0cm;margin-left:36.45pt;margin-bottom:.0001pt;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'>      // 
-+------------------------------------------------------------------------------+<o:p></o:p>
+style='color:green'>//  +------------------------------------------------------------------------------+<o:p></o:p>

<p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
mso-layout-grid-align:none;text-autospace:none'>     //  +------------------------------------------------------------------------------+<o:p></o:p>
+style='color:green'>// 
++------------------------------------------------------------------------------+<o:p></o:p>

<p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
mso-layout-grid-align:none;text-autospace:none'>ActionSequence) separated by a comma.
-The first transition does just this: 2 actions separated by a comma and
-enclosed inside parenthesis to respect C++ operator precedence.<o:p></o:p>
+The first transition does just this: 2 actions separated by a comma and enclosed
+inside parenthesis to respect C++ operator precedence.<o:p></o:p>

Notice the parenthesis
@@ -10397,8 +10532,8 @@

The only differences with our
-previous functors is that they return a bool (guards are in UML actions
-returning a bool and producing no side-effect), and they must inherit from euml_action in order to enable the grammar. The
same is also necessary for events which must inherit from euml_event:<o:p></o:p>
@@ -10515,10 +10650,9 @@
EN-US;mso-no-proof:yes'>A NoAction is also defined, which does, well,
-nothing except being a placeholder (needed for example as entry action if we
-have no entry but an exit).<o:p></o:p>
+mso-ansi-language:EN-US;mso-no-proof:yes'> is also defined, which does, well, nothing
+except being a placeholder (needed for example as entry action if we have no
+entry but an exit).<o:p></o:p>

Expr1<o:p> </o:p>

Likewise, eUML provides other
-state-building functions for other types of states:<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>Likewise, eUML provides other state-building
+functions for other types of states:<o:p></o:p>

<span
lang=EN-US style='font-family:"Courier New";mso-fareast-font-family:"Times New Roman";
@@ -10681,8 +10815,8 @@
Sometimes you might want to define
the same way a state machine on the fly (if, for example, you need to provide
-an on_entry/on_exit for this state machine as a functor). For this, there is also
-a function, build_sm, which has up to 8 arguments:<o:p></o:p>

@@ -11180,10 +11314,10 @@

A fork is a direct entry into
-several regions of a composite substate. EUML also supports this by allowing
-the user to define a list of entry states separated by a comma and enclosed
-inside parenthesis, for eaxample:<o:p></o:p>
+EN-US;mso-no-proof:yes'>A fork is a direct entry into several
+regions of a composite substate. EUML also supports this by allowing the user
+to define a list of entry states separated by a comma and enclosed inside
+parenthesis, for eaxample:<o:p></o:p>

        get_attributes<0>()=name;<o:p></o:p>
+style='mso-spacerun:yes'>        get_attributes<0>()=name;<o:p></o:p>

<p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
mso-layout-grid-align:none;text-autospace:none'>                                
-attributes_ << no_attributes_,<o:p></o:p>
+style='mso-spacerun:yes'>              
+                  attributes_ << no_attributes_,<o:p></o:p>

<p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
mso-layout-grid-align:none;text-autospace:none'>EUML also supports defining <a
-href="#_Orthogonal_States_(+Defer">deferred events</a> in the state (state
-machine) definition. To this aim, we can reuse the previous flag grammar. For
-example:<o:p></o:p>
+href="#_Orthogonal_States_(+Defer">deferred events</a> in the state (state machine)
+definition. To this aim, we can reuse the previous flag grammar. For example:<o:p></o:p>

<o:p> </o:p>
@@ -12091,8 +12224,7 @@
<p class=MsoNormal style='margin-top:12.0pt;margin-right:36.45pt;margin-bottom:
0cm;margin-left:36.45pt;margin-bottom:.0001pt;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'>#include <
-msm/front/euml/operator.hpp><o:p></o:p>
+"Times New Roman";color:black;mso-ansi-language:EN'>#include < msm/front/euml/operator.hpp><o:p></o:p>

<p class=MsoNormal style='margin-top:12.0pt;margin-right:36.45pt;margin-bottom:
0cm;margin-left:36.45pt;margin-bottom:.0001pt;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'>·       <![endif]>if_then_(guard,
-action) where guard
-respects the guard grammar and action the action sequence grammar.<o:p></o:p>
+action) where guard respects
+the guard grammar and action the action sequence grammar.<o:p></o:p>

<p style='margin-top:5.0pt;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;
margin-bottom:.0001pt;text-indent:-18.0pt;mso-list:l45 level1 lfo33;tab-stops:
@@ -12268,7 +12400,8 @@
String_<mpl::string<’Hell’,’o
wo’,’rld’> >(). Please refer to the <a
href="http://www.boost.org/doc/libs/1_40_0/libs/mpl/doc/refmanual/string.html">MPL
-documentation</a>. This is the one case where you will see some Metaprogramming.<o:p></o:p>
+documentation</a>. This is the one case where you will see some
+Metaprogramming.<o:p></o:p>

</o:p>

Notice that we have lots of operators,
-functors and functions like build_stt but all is compile-time, there is no run-time penalty as the code is
-not really called but simply evaluated. Now try to do this with your local
-javac compiler…<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>Notice that we have lots of
+operators, functors and functions like build_stt but all is compile-time, there is
+no run-time penalty as the code is not really called but simply evaluated. Now
+try to do this with your local javac compiler…<o:p></o:p>

The following table lists the
@@ -13176,8 +13309,8 @@
 mso-border-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 <p style='margin-bottom:0cm;margin-bottom:.0001pt;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
 mso-yfti-cnfc:68'>[] (works on vector,
- map, arrays)<o:p></o:p>
+ lang=EN style='mso-ansi-language:EN;mso-bidi-font-weight:bold'>(works on
+ vector, map, arrays)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border-top:solid #4F81BD 1.0pt;
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
@@ -13364,8 +13497,8 @@
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
 Returns the some_int attribute of the
- source state from the currently triggered transition.<o:p></o:p>
+ lang=EN style='mso-ansi-language:EN'>Returns the some_int attribute of the source
+ state from the currently triggered transition.<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
 
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
 Returns the some_int attribute of the current
- state (valid inside an entry/exit state action).<o:p></o:p>
+ lang=EN style='mso-ansi-language:EN'>Returns the some_int attribute of the
+ current state (valid inside an entry/exit state action).<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
 <span lang=EN-US style='mso-fareast-font-family:"Times New Roman";
@@ -13482,8 +13615,8 @@
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
 mso-border-bottom-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 <p style='margin-bottom:0cm;margin-bottom:.0001pt;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
- mso-yfti-cnfc:64'>Wrappers around
- the value some_int<o:p></o:p>
+ mso-yfti-cnfc:64'>Wrappers around the
+ value some_int<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border-top:solid #4F81BD 1.0pt;
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
@@ -13576,8 +13709,8 @@
 mso-border-bottom-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 <p style='margin-bottom:0cm;margin-bottom:.0001pt;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
 mso-yfti-cnfc:64'>Processes Event
- on the current state machine (if no fsm specified) or on up to 4 state
- machines returned by an appropriate functor.<o:p></o:p>
+ on the current state machine (if no fsm specified) or on up to 4 state machines
+ returned by an appropriate functor.<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border-top:solid #4F81BD 1.0pt;
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
@@ -13798,9 +13931,9 @@
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
 mso-border-bottom-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 <p style='margin-bottom:0cm;margin-bottom:.0001pt;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
- mso-yfti-cnfc:64'>Returns the
- current state machine (as reference). Valid inside a state entry/exit action
- or a transition.<o:p></o:p>
+ mso-yfti-cnfc:64'>Returns the current
+ state machine (as reference). Valid inside a state entry/exit action or a
+ transition.<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border-top:solid #4F81BD 1.0pt;
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
@@ -14111,12 +14244,12 @@
lang=EN-US style='mso-ansi-language:EN-US'><o:p></o:p>

Your functors will usually not need
-this. You will only need these extra declarations if your functors are to be
-used in combination with eUML functions (if_then_else_ , STL algorithms) or
-operators returning a value (++, +=, etc.). If you simply need simple guards
-/actions like [Condition1() && Condition2()] / (Action1(),Action2()),
-you do not need to declare the return type.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>Your functors will usually not need this.
+You will only need these extra declarations if your functors are to be used in
+combination with eUML functions (if_then_else_ , STL algorithms) or operators
+returning a value (++, +=, etc.). If you simply need simple guards /actions
+like [Condition1() && Condition2()] / (Action1(),Action2()), you do not
+need to declare the return type.<o:p></o:p>

This declaration is not very nice
@@ -14177,8 +14310,8 @@

In a nutshell, almost every STL
-method or algorithm is matched by a corresponding functor, which can then be
-used in the transition table or state actions. The following tables explain in
+method or algorithm is matched by a corresponding functor, which can then be used
+in the transition table or state actions. The following tables explain in
detail the possible argument combination and the underlying functor, so that
this possibility is not reserved to eUML but also to the functor-based
front-end previously explained.<o:p></o:p>
@@ -14348,8 +14481,7 @@
 accent1;border-bottom:none;border-right:none;background:#4F81BD;mso-background-themecolor:
 accent1;padding:0cm 5.4pt 0cm 5.4pt'>
 STL functions in
- querying.hpp<o:p></o:p>
+ white;mso-themecolor:background1;mso-ansi-language:EN'>STL functions in querying.hpp<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;border-top:solid #4F81BD 1.0pt;
 mso-border-top-themecolor:accent1;background:#4F81BD;mso-background-themecolor:
@@ -17567,13 +17699,13 @@
<p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
mso-layout-grid-align:none;text-autospace:none'>    int
-foo(int i)const {std::cout
-<< "foo(int):" << i << std:: 
+  int foo(int i)const {std::cout << "foo(int):"
+<< i << std::endl; return 1;}<o:p></o:p>

<p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
@@ -17825,8 +17957,8 @@

On VC9, the test state machines used
-in the performance section produce executables of 14kB (for simple and eUML) and
-21kB (for the composite). This includes the test code and iostreams. By
+in the performance section produce executables of 14kB (for simple and eUML)
+and 21kB (for the composite). This includes the test code and iostreams. By
comparison, an empty executable with iostreams generated by VC9 has a size of
7kB. Boost.Statechart generates executables of 43kB and 54kB. As a bonus, eUML
comes for “free” in terms of executable size. You even get a speed
@@ -17910,9 +18042,9 @@
style='mso-list:Ignore'>·       
<![endif]>Compilation
times that are going to make you storm the CFO's office and make sure you get a
-shiny octocore with 8GB RAM by next week, unless he's interested in paying you
-watch the compiler agonize for hours... (Make sure you ask for dual 24" as
-well, it doesn't hurt).<o:p></o:p>
+shiny octocore with 8GB RAM by next week, unless he's interested in paying you watch
+the compiler agonize for hours... (Make sure you ask for dual 24" as well,
+it doesn't hurt).<o:p></o:p>

<![if !supportLists]>::type>::type, 
                                                            typename
-::boost::mpl::not_<typename is_pseudo_exit<StateType>::type>::type 
+style='mso-spacerun:yes'>                    
+typename ::boost::mpl::not_<typename
+is_pseudo_exit<StateType>::type>::type 
        >::type,BaseState*>::type<o:p></o:p>

I only found two ways to break the
compiler:<o:p></o:p>

-<p style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l36 level1 lfo48;
+<p style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l36 level1 lfo43;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·Add more eUML constructs until
something explodes. <o:p></o:p>

-<p style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l36 level1 lfo48;
+<p style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l36 level1 lfo43;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·Msm2:<o:p></o:p></h2>

-<![if !supportLists]><![endif]>eUML
was made possible by Boost.Proto and Boost.Typeof<o:p></o:p>

-<![if !supportLists]><![endif]>Thanks
to Eric Niebler for his patience correcting my grammar errors<o:p></o:p>

-<![if !supportLists]>J<o:p></o:p>

-<![if !supportLists]></o:p>

+<![if !supportLists]>·       
+<![endif]>Thanks
+to the ones who gave some review comments and helped find problems: Juraj
+Ivancic, Andreas Huber.<o:p></o:p>
+
<h2 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'>Msm1</h2>

-<![if !supportLists]></o:p>

-<![if !supportLists]></o:p>

-<![if !supportLists]>Used libraries:<o:p></o:p></h1>

-<p class=MsoListParagraphCxSpFirst style='text-indent:-18.0pt;mso-list:l4 level1 lfo44;
+<p class=MsoListParagraphCxSpFirst style='text-indent:-18.0pt;mso-list:l4 level1 lfo45;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·       <![endif]>Boost::bind<o:p></o:p>

-<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo44;
+<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo45;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·       <![endif]>Boost::mpl<o:p></o:p>

-<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo44;
+<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo45;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·       <![endif]>Boost::fusion<o:p></o:p>

-<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo44;
+<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo45;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·       <![endif]>Boost::proto<o:p></o:p>

-<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo44;
+<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo45;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·       <![endif]>Boost::typeof<o:p></o:p>

-<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo44;
+<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo45;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·       <![endif]>Boost:TypeTraits<o:p></o:p>

-<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo44;
+<p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt;mso-list:l4 level1 lfo45;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·       <![endif]>Boost::utility<o:p></o:p>

-<p class=MsoListParagraphCxSpLast style='text-indent:-18.0pt;mso-list:l4 level1 lfo44;
+<p class=MsoListParagraphCxSpLast style='text-indent:-18.0pt;mso-list:l4 level1 lfo45;
tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><![if !supportLists]>·Answer: Msm uses Boost.MPL under the hood and this is
-the default maximum size. Please define the following 2 macros before including
+the default maximum size. Please define the following 3 macros before including
any Msm headers:<o:p></o:p>

<div id=limit-vector-size>
@@ -18298,6 +18439,7 @@
<div id=configuration-limit-example><pre>#define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS<o:p></o:p></pre><pre>#define BOOST_MPL_LIMIT_VECTOR_SIZE 30 // or whatever you need<o:p></o:p></pre><pre>#define BOOST_MPL_LIMIT_MAP_SIZE 30 // or whatever you need<o:p></o:p></pre><pre><o:p> </o:p></pre></div>

</div>
@@ -18337,8 +18479,8 @@
"Times New Roman";mso-ansi-language:EN-US'>Explicit Entry vs Orthogonal zones<o:p></o:p></h2>

Let us try to implement the state
-machine defined in a paper from David Harel (Figure 8 in <a
+lang=EN-US style='mso-ansi-language:EN-US'>Let us try to implement the state machine
+defined in a paper from David Harel (Figure 8 in <a
href="http://www.wisdom.weizmann.ac.il/~dharel/SCANNED.PAPERS/Statecharts.pdf">http://www.wisdom.weizmann.ac.il/~dharel/SCANNED.PAPERS/Statecharts.pdf>).<o:p></o:p>

<span
@@ -18367,12 +18509,12 @@
“alarm-beeps” has an implementation visible to the outside world.
This particularity is being used and this leads to three states with close
names, “alarm1 beeps”, “alarm2 beeps”, “both
-beep”. If you think that this starts sounding like duplication of
-information, you are not the only one. The second point is about design and
-reuse. Let us imagine what could happen if Harel really was working for a
-company producing watches.<o:p></o:p>
+beep”. If you think that this starts sounding like duplication of information,
+you are not the only one. The second point is about design and reuse. Let us
+imagine what could happen if Harel really was working for a company producing
+watches.<o:p></o:p>

-<![if !supportLists]><![endif]>Harel
would implement this state machine.<o:p></o:p>

-<![if !supportLists]></o:p>

-<![if !supportLists]><![endif]>Or
maybe 4 alarms?<o:p></o:p>

-<![if !supportLists]>What would be the result? New states
like “alarm3 beeps” or “three beep” + “both
beep” (backward compatibility). Maintenance would quickly become a
-nightmare. The reason? A breach of encapsulation caused by “alarm
-beeps” letting other state machines use its internals.<o:p></o:p>
+nightmare. The reason? A breach of encapsulation caused by “alarm beeps”
+letting other state machines use its internals.<o:p></o:p>

Luckily, UML provides not only the
@@ -18429,7 +18571,7 @@
Let us redesign Alarm-Beeps by:<o:p></o:p>

-<![if !supportLists]><![endif]>Encapsulating
the alarm functionality in its own state (machine).<o:p></o:p>

-<![if !supportLists]>Which of both methods should you
use? It is a matter of taste and you will hear different opinions from
different designers. If you need something fast and with a short life cycle,
-then you could consider the method with explicit entries. If you are more
-interested in reusable design, then the method using instances is for you. The
-personal preference of the author goes to, you guessed it, the second one.<o:p></o:p>
+then you could consider the method with explicit entries. If you are more interested
+in reusable design, then the method using instances is for you. The personal
+preference of the author goes to, you guessed it, the second one.<o:p></o:p>

<h1 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_EUML_Case_Studies"></a>eUML
@@ -18673,8 +18815,8 @@
lang=EN-US style='mso-ansi-language:EN-US'> contains a counter, which is
initialized with the event countdown data (start_timer.m_timer) in the action method (written after
-a slash) of the transition fired by the ) in the action method (written
+after a slash) of the transition fired by the start_timer event. <o:p></o:p>

@@ -18847,8 +18989,8 @@
lang=EN-US style='mso-ansi-language:EN-US'>The previous example is a standard
application for state machines. But we want to push our model-driven approach
further by using a state machine to write an algorithm. I already see some at
-the back of the room looking perplexed. Well, why not? Usually, UML designers
-like to use Activity Diagrams to do this, but mostly for documentation purposes
+the back of the room looking perplexed. Well, why not? Usually, UML designers like
+to use Activity Diagrams to do this, but mostly for documentation purposes
because Activity Diagrams are hard to define with a precision needed for
automatic code generation. On the other hand, state machines have a very strict
formalism which enables code generation while being “cousin” with
@@ -18931,9 +19073,9 @@
lang=EN-US style='mso-ansi-language:EN-US'><o:p> </o:p>

While this clearly intends to start building
-an algorithm library, this example will be kept not generic to display the use
-of eUML.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>While this clearly intends to start
+building an algorithm library, this example will be kept not generic to display
+the use of eUML.<o:p></o:p>

<o:p> </o:p>
@@ -19031,9 +19173,9 @@
mso-layout-grid-align:none;text-autospace:none'>                            
+style='mso-spacerun:yes'>                                    
                      process2_(OneSong(),*(State_<m_src_it>()++)) ),<o:p></o:p>
@@ -19257,8 +19399,8 @@
#030003'>Insert;<o:p></o:p>

This state has no attribute and simply
-calls the function This state has no attribute and
+simply calls the function push_back_(container, element) on the state machine’s result list, then
sends a Done event, thus moving back to Foreach, which will send the next song,
@@ -19337,9 +19479,10 @@
<p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
mso-layout-grid-align:none;text-autospace:none'>      //  +------------------------------------------------------------------------------+<o:p></o:p>
+mso-ansi-language:EN-US;mso-no-proof:yes'> 
+    // 
++------------------------------------------------------------------------------+<o:p></o:p>

<p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
mso-layout-grid-align:none;text-autospace:none'>                               
-init_ << Foreach(), // Init<o:p></o:p>
+style='mso-spacerun:yes'>                             
+  init_ << Foreach(),
+// Init<o:p></o:p>

<p class=MsoNormal style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
mso-layout-grid-align:none;text-autospace:none'>                              
+style='mso-spacerun:yes'>                      
             <<
+style='mso-spacerun:yes'>                     <<
vector<OneSong>()
/*m_tgt_container*/, //
result<o:p></o:p>
@@ -19481,8 +19625,8 @@
style='font-family:"Courier New";mso-ansi-language:EN-US'>ErrorMode id 6 and SleepMode (seen only in the “Next”
-column) id 7.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'> (seen only in the
+“Next” column) id 7.<o:p></o:p>

If you have some implicitly created
@@ -19492,8 +19636,8 @@
source at the end of the transition table.<o:p></o:p>

If you have composite states, a row will
-be added for them at the end of the table, after the automatically or
+lang=EN-US style='mso-ansi-language:EN-US'>If you have composite states, a row
+will be added for them at the end of the table, after the automatically or
explicitly created states, which can change their id.<o:p></o:p>

To achieve this, Msm provides a few
useful tools:<o:p></o:p>

-<![if !supportLists]>: returns a mpl::set of all the
states defined in the table.<o:p></o:p>

-<![if !supportLists]>: returns a mpl::set of all the
events defined in the table.<o:p></o:p>

-<![if !supportLists]>mpl::size<>::value you can get the number of elements in the set.<o:p></o:p>

-<![if !supportLists]>cout.<o:p></o:p>

-<![if !supportLists]> as argument will display all the
states of the state machine.<o:p></o:p>

-<![if !supportLists]>·       
<![endif]>Let's
-suppose you need even more and recursively find the states and events defined in
-the composite states and thus also having a transition table. No problem!
+suppose you need even more and recursively find the states and events defined
+in the composite states and thus also having a transition table. No problem!
Calling recursive_get_transition_table<Composite> will return you the transition table of the

Next message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r57649 - sandbox/stm/branches/vbe/libs/stm/example/tx"
Previous message: vicente.botet_at_[hidden]: "[Boost-commit] svn:boost r57647 - in sandbox/stm/branches/vbe: boost/stm/tx libs/stm/example/tx"

Date view	Thread view	Subject view	Author view

Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk