Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r57822 - in sandbox/msm/libs/msm/doc: . index-Dateien
From: christophe.j.henry_at_[hidden]
Date: 2009-11-20 15:45:03

Next message: christophe.j.henry_at_[hidden]: "[Boost-commit] svn:boost r57823 - in sandbox/msm/libs/msm/doc: . index-Dateien"
Previous message: christophe.j.henry_at_[hidden]: "[Boost-commit] svn:boost r57821 - sandbox/msm/boost/msm/front/euml"

Author: chenry
Date: 2009-11-20 15:45:02 EST (Fri, 20 Nov 2009)
New Revision: 57822
URL: http://svn.boost.org/trac/boost/changeset/57822

Log:
fixed no_transition doc error
Text files modified:
   sandbox/msm/libs/msm/doc/index-Dateien/props0033.xml | 2
   sandbox/msm/libs/msm/doc/index.htm | 630 +++++++++++++++++++--------------------
   2 files changed, 313 insertions(+), 319 deletions(-)

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-20 15:45:02 EST (Fri, 20 Nov 2009)
@@ -1,2 +1,2 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<ds:datastoreItem ds:itemID="{5D53E1BA-76C2-4B61-A162-F608A44C098C}" 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="{6361FD76-1A79-4CC6-9F4B-E43CA6B60F5E}" 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-20 15:45:02 EST (Fri, 20 Nov 2009)
@@ -23,15 +23,15 @@
 <o:Author>Christophe</o:Author>
 <o:Template>Normal</o:Template>
 <o:LastAuthor>Christophe</o:LastAuthor>
- <o:Revision>280</o:Revision>
+ <o:Revision>283</o:Revision>
 <o:Created>2009-09-03T20:17:00Z</o:Created>
- <o:LastSaved>2009-11-15T22:56:00Z</o:LastSaved>
+ <o:LastSaved>2009-11-20T20:29:00Z</o:LastSaved>
 <o:Pages>39</o:Pages>
- <o:Words>18953</o:Words>
- <o:Characters>119404</o:Characters>
+ <o:Words>18955</o:Words>
+ <o:Characters>119422</o:Characters>
 <o:Lines>995</o:Lines>
 <o:Paragraphs>276</o:Paragraphs>
- <o:CharactersWithSpaces>138081</o:CharactersWithSpaces>
+ <o:CharactersWithSpaces>138101</o:CharactersWithSpaces>
 <o:Version>12.00</o:Version>
 </o:DocumentProperties>
</xml><![endif]-->
@@ -1785,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;}
@@ -4998,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"/>
@@ -5504,8 +5505,8 @@
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
@@ -5516,9 +5517,9 @@
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>
+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>
@@ -5560,9 +5561,9 @@
(Action1(),Action2())<o:p></o:p>

UML
-designers are also used to write pseudo-code in the action methods, like
-++counter. This is now also possible, along with most of the STL algorithms or
-container methods.<o:p></o:p>
+designers are also used to write pseudo-code in the action methods, like ++counter.
+This is now also possible, along with most of the STL algorithms or container
+methods.<o:p></o:p>

To
achieve this, eUML also acts like a compile-time boost::phoenix adapted to the
@@ -5816,9 +5817,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>
@@ -6551,8 +6552,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"
@@ -6764,34 +6766,29 @@
style='mso-ansi-language:EN-US'><o:p></o:p>

<code>// Replaces the
-default no-transition response.</code>// Replaces the default
+no-transition response.</code><o:p></o:p>

-<code>template</code><code> <</code><code>class</code><code> </code><code>Event</code><code>></code><o:p></o:p>
-
-<code>int</code><code> </code><code>no_transition</code><code>(</code><code>template <class FSM,class Event> <code>int</code><code> </code><code>state</code><code>, </code><code>Event</code><code> </code><code>const</code><code>& </code><code>e</code><code>){</code><code>no_transition</code><code>(</code>Event const& e, FSM&,int state<code>){</code><code>...}</code><o:p></o:p>
@@ -6911,7 +6908,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>
@@ -6939,8 +6937,9 @@
style='font-size:10.0pt;color:#030003;mso-ansi-language:EN-US'>player_</code><code> : </code><code>public</code><code> msm::front::</code><code>state_machine_def</code><code>
+msm::front::</code><code>state_machine_def</code><code><</code><code>player_</code><code>>{...}</code><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>

-This tutorial will
-demonstrate the use of three more features that UML defines: Othogonal regions,
-deferring of events and terminate States.<o:p></o:p>
+This tutorial will demonstrate
+the use of three more features that UML defines: Othogonal regions, deferring
+of events and terminate States.<o:p></o:p>

It is a very common problem
in many state machines to have to handle errors. It usually involves defining a
@@ -7217,9 +7216,9 @@

Usually, when you get an
error, you do not want other events to be handled. To achieve this, we use
-another UML feature, terminate states. When any region moves to a terminate
-state, the state machine “terminates” (the state machine and all
-its states stay alive) and all further events are ignored.<o:p></o:p>
+another UML feature, terminate states. When any region moves to a terminate state,
+the state machine “terminates” (the state machine and all its
+states stay alive) and all further events are ignored.<o:p></o:p>

This is of course not
mandatory, one can use orthogonal regions without terminate states.<o:p></o:p>
@@ -7234,8 +7233,8 @@
lang=EN-US style='mso-ansi-language:EN-US'> as interrupt state instead, the
state machine will not handle any event other than the one which ends the
interrupt. So it's like a terminate state, with the difference that you are
-allowed to resume the state machine when a condition (like handling of the original
-error) is met.<o:p></o:p>
+allowed to resume the state machine when a condition (like handling of the
+original error) is met.<o:p></o:p>

<o:p> </o:p>

@@ -7331,8 +7330,8 @@
12.0pt;font-family:"Times New Roman","serif";color:#030003;mso-ansi-language:
EN-US'>And you're done with the orthogonal regions! You don't have to give the
regions an id but be advised that there is currently no compile time
-enforcement of region consistency (Msm does not yet check that the regions are
-truly orthogonal)</code><o:p></o:p>
+enforcement of region consistency (Msm does not yet check that the regions are truly
+orthogonal)</code><o:p></o:p>

<o:p> </o:p>

@@ -7448,9 +7447,9 @@

As explained in the <a
href="MsmSession_Handout.pdf">BoostCon09 paper</a>, Histories are weird. First,
-there can be just one. And they can have only one out transition, so if you
-have orthogonal regions, you are out of luck. They also replace the initial
-state symbol. And if you have deep policy, things become much worse because you
+there can be just one. And they can have only one out transition, so if you have
+orthogonal regions, you are out of luck. They also replace the initial state
+symbol. And if you have deep policy, things become much worse because you
cannot easily draw a line into a submachine. To make it worse, they are not
exactly object-oriented as a on the picture, a transition should have been
drawn directly into Playing, with the History as target.<o:p></o:p>
@@ -7493,8 +7492,8 @@
"Courier New";mso-ansi-language:EN-US'>Playing state machine gets activated by the end_pause event and only this one (or any
-other event added to the mpl::vector). If the state machine was in the event and only this one (or any other
+event added to the mpl::vector). If the state machine was in the Stopped state and the event playFlags.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>
+So what is it and what is its
+use?<o:p></o:p>

If you look into the
Boost.Statechart documentation you'll find some code like:<o:p></o:p>
@@ -7568,8 +7567,8 @@
style='color:blue'>Playing * >() != 0 ) )<o:p></o:p></pre>

Or flag these 4 states as
-CDLoaded-able. You can do it like this:<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>Or flag these 4 states as CDLoaded-able.
+You can do it like this:<o:p></o:p>

<code>typedef</code><code>And what if you have orthogonal
-regions? How to decide if a state machine is in a flagged state? By default, you
-keep the same code and the current states will be OR'ed, meaning if one of the
-active states has the flag, then <span lang=EN-US style='font-family:
+regions? How to decide if a state machine is in a flagged state? By default,
+you keep the same code and the current states will be OR'ed, meaning if one of
+the active states has the flag, then is_flag_active returns true. Of course, in some cases, you
might want that all of the active states are flagged for the state to be
@@ -7694,8 +7693,8 @@
Anonymous transitions are
transitions without a named event. This means that the transition automatically
-fires when the predecessor state is entered (to be exact, after the entry condition).
-Otherwise it is a normal transition with actions and guards. <o:p></o:p>
+fires when the predecessor state is entered (to be exact, after the entry
+condition). Otherwise it is a normal transition with actions and guards. <o:p></o:p>

Why would you need something like
@@ -7755,8 +7754,7 @@
style='mso-spacerun:yes'>        , State4 
, State3ToState4      ,       , always_true         
><o:p></o:p>
@@ -7889,8 +7887,8 @@
Symbol;mso-bidi-font-family:Symbol;mso-ansi-language:EN-US'>·       
<![endif]>Exit
-point pseudo state: connects one transition inside a composite state to a transition
-outside the composite and leading to another (outside) state.<o:p></o:p>
+point pseudo state: connects one transition inside a composite state to a
+transition outside the composite and leading to another (outside) state.<o:p></o:p>

<o:p> </o:p>
@@ -8010,8 +8008,8 @@
mso-ansi-language:EN-US'>PseudoExit1, triggered by event5 and connecting two transitions using the same event. Again, the event is
-forwarded to the second transition and both regions are exited, as and connecting two transitions using the same event. Again, the event
+is forwarded to the second transition and both regions are exited, as SubFsm2 becomes inactive. Note that if no
transition is defined from Fork<o:p></o:p></h4>

Need a fork instead of an
-explicit entry? Then, as a fork is an entry into states of different regions,
-we need to give it a list of target states:Need a fork instead of
+an explicit entry? Then, as a fork is an entry into states of different
+regions, we need to give it a list of target states:<o:p></o:p>

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width="100%"
@@ -8255,9 +8253,9 @@
lang=EN-US style='mso-ansi-language:EN-US'><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>
@@ -8296,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>
@@ -8454,8 +8452,8 @@
Important note 1: UML defines transiting to an entry
-pseudo state and having either no second transition or one with a guard as an error
-but defines no error handling. Msm will tolerate this behavior; the entry
+pseudo state and having either no second transition or one with a guard as an
+error but defines no error handling. Msm will tolerate this behavior; the entry
pseudo state will simply be the newly active state.<o:p></o:p>

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>
+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>

There are two kinds of conflicts,
@@ -8704,14 +8702,14 @@
Msm v2.0 but made obsolete by the fact that every guard/action/entry
action/exit action get the state machine passed as argument.<o:p></o:p>

-All of the states defined in the state machine are created upon program
-initialization. This has the huge advantage of a reduced syntactic noise. The
-cost is a small loss of control of the user on the state creation and access. Quite
-fast came from the beta testers the request of a way for a state to get access
-to its containing state machine. This is implemented via another policy.
-Basically, a state needs to change its declaration to:<o:p></o:p>
+All of the states defined in the
+state machine are created upon state machine construction. This has the huge
+advantage of a reduced syntactic noise. The cost is a small loss of control of
+the user on the state creation and access. Quite fast came from the beta
+testers the request of a way for a state to get access to its containing state
+machine. This is implemented via another policy. Basically, a state needs to
+change its declaration to:<o:p></o:p>

<code><span lang=EN-US style='font-size:10.0pt;
@@ -8837,9 +8835,9 @@

<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
+font-family:"Times New Roman","serif";mso-ansi-language:EN-US'>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
set it straight by catching std::exception and calling: </code><o:p></o:p>

@@ -8954,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>

process_event</code><code> </code><code>can
-execute up to 4 times faster. On a Q6600, an average transition execution lasts
-45ns with a full state machine, 10ns in the minimal case.</code>can execute
+up to 4 times faster. On a Q6600, an average transition execution lasts 45ns
+with a full state machine, 10ns in the minimal case.</code><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
@@ -9164,9 +9162,9 @@
Symbol;mso-ansi-language:EN-US'>·       <![endif]>Use a functor “<a
-href="#_Functor_rows">Row</a>” transition. These rows offer an FSM template
-argument. This argument is the concrete (back-end) state machine on which
-process_event can be called.<o:p></o:p>
+href="#_Functor_rows">Row</a>” transition. These rows offer an FSM
+template argument. This argument is the concrete (back-end) state machine on
+which process_event can be called.<o:p></o:p>

<p class=MsoListParagraphCxSpLast style='text-indent:-18.0pt;mso-list:l6 level1 lfo23;
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>

typedef msm::back::state_machine<player_
-> player;<o:p></o:p>
+lang=EN-US style='font-family:"Courier New";mso-ansi-language:EN-US'>typedef
+msm::back::state_machine<player_ > player;<o:p></o:p>

player
@@ -9321,11 +9319,11 @@
12.0pt;mso-bidi-font-size:12.0pt;color:black;mso-ansi-language:EN-US'>my_base_state</code><code> </code><code>is your
-new base state. If it has a virtual function, your states become polymorphic.
-Msm also provides a default polymorphic base type for your convenience, </code><code>msm::front::polymorphic_</code><code>is
+your new base state. If it has a virtual function, your states become
+polymorphic. Msm also provides a default polymorphic base type for your
+convenience, </code><code>msm::front::polymorphic_</code><code>state</code><o:p></o:p>
@@ -10025,9 +10023,9 @@
lang=EN-US style='font-family:Symbol;mso-fareast-font-family:Symbol;mso-bidi-font-family:
Symbol;mso-ansi-language:EN-US'>·       <![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]>    void
+style='mso-spacerun:yes'>    void
operator()(FSM&
fsm,EVT const& ,SourceState&
@@ -10118,9 +10115,8 @@
"Times New Roman";mso-ansi-language:EN-US;mso-no-proof:yes'><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
@@ -10151,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
@@ -10199,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'><span
@@ -10537,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>
@@ -10575,8 +10570,8 @@
lang=EN-US style='mso-ansi-language:EN-US'><o:p></o:p>

This means that Empty is defined as a
-state with an entry action made of two sub-actions, This means that Empty is defined as
+a state with an entry action made of two sub-actions, Empty_Entry and Dummy_Entry 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";
@@ -10853,9 +10847,9 @@
build_sm(Stt,
Init, Expr1, Expr2, Attributes, Configure): state machine where the transition table, initial
-state, entry and exit actions are defined. Furthermore, some attributes (read
-further on): state machine where the transition table,
+initial state, entry and exit actions are defined. Furthermore, some attributes
+(read further on), flags, deferred events and <a
href="#_Customizing_a_state">configuration capabilities</a> (no message queue /
no exception catching) are
@@ -11320,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>

<span
lang=EN-US style='mso-fareast-font-family:"Times New Roman";mso-ansi-language:
@@ -11923,9 +11917,8 @@

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>
@@ -12231,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>

</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
@@ -12998,7 +12990,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'>Action1() * Action2()<o:p></o:p>
+ mso-yfti-cnfc:64'>Action1() *
+ Action2()<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:solid #4F81BD 1.0pt;
 mso-border-themecolor:accent1;border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -13134,7 +13127,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'>Calls lazily -Action1<o:p></o:p>
+ mso-yfti-cnfc:64'>Calls lazily
+ -Action1<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;
@@ -13356,8 +13350,8 @@
 mso-ansi-language:EN-US'>if_then_else_(Condition1(),++Source_<0>(),<o:p></o:p>
                                                --Source_<0>())<o:p></o:p>
+ style='mso-spacerun:yes'>                                              
+ --Source_<0>())<o:p></o:p>
 [if_then_else_(Condition1(),True_(), False())]<o:p></o:p>
 </td>
@@ -13479,8 +13473,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'>Returns the some_int
- attribute of the currently processed event.<o:p></o:p>
+ mso-yfti-cnfc:64'>Returns the
+ some_int attribute of the currently processed event.<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;
@@ -13503,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'>
 <span lang=EN-US style='mso-fareast-font-family:"Times New Roman";
@@ -13621,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;
@@ -13715,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;
@@ -13745,9 +13739,9 @@
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
 Processes Event on the current state machine
- (if no fsm specified) or on up to 2 state machines returned by an appropriate
- functor. The event is copy-constructed from what Data() returns.<o:p></o:p>
+ lang=EN style='mso-ansi-language:EN'>Processes Event on the current state
+ machine (if no fsm specified) or on up to 2 state machines returned by an
+ appropriate functor. The event is copy-constructed from what Data() returns.<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 style='mso-fareast-font-family:"Times New Roman";
@@ -13937,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;
@@ -14250,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
@@ -14316,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>
@@ -14378,15 +14372,14 @@
<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/container.hpp><o:p></o:p>
+"Times New Roman";color:black;mso-ansi-language:EN'>#include < msm/front/euml/container.hpp><o:p></o:p>

<o:p> </o:p>

Or one can simply include the whole STL support
-(you will also need to include euml.hpp):<o:p></o:p>
+lang=EN style='mso-ansi-language:EN'>Or one can simply include the whole STL
+support (you will also need to include euml.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'>
 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:
@@ -15522,8 +15514,8 @@
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;border-bottom:
 solid #4F81BD 1.0pt;mso-border-bottom-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
- rotate_(first,
- middle, last)ᵇ<o:p></o:p>
+ rotate_(first, middle,
+ last)ᵇ<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border-top:none;border-left:
 none;border-bottom:solid #4F81BD 1.0pt;mso-border-bottom-themecolor:accent1;
@@ -16274,8 +16266,8 @@
 EN'>void erase(pos)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- void
- associative_erase_( container , pos)<o:p></o:p>
+ void associative_erase_(
+ container , pos)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -16527,8 +16519,8 @@
 EN'>int compare(string)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- int
- string_compare_(container, another_string)<o:p></o:p>
+ int string_compare_(container,
+ another_string)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -16598,8 +16590,8 @@
 EN'>string& append(const string&)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- string&
- append_(container, another_string)<o:p></o:p>
+ string& append_(container,
+ another_string)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -16982,8 +16974,8 @@
 <td width=437 valign=top style='width:261.95pt;border:solid #4F81BD 1.0pt;
 mso-border-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 string& replace(iterator first, iterator last,
- const charT*, size_type n)<o:p></o:p>
+ style='mso-ansi-language:EN'>string& replace(iterator first, iterator
+ last, const charT*, size_type n)<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;
@@ -17004,8 +16996,8 @@
 EN'>string& replace(iterator first, iterator last, const charT*)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- string&
- string_replace_(container, first, last, another_string)<o:p></o:p>
+ string& string_replace_(container,
+ first, last, another_string)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -17039,8 +17031,8 @@
 l)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- string& string_replace_(container,
- first, last, f, l)<o:p></o:p>
+ string&
+ string_replace_(container, first, last, f, l)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -17072,8 +17064,7 @@
 EN'>const charT* data()<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- const charT*
- string_data_(container)<o:p></o:p>
+ const charT* string_data_(container)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -17084,8 +17075,8 @@
 <td width=437 valign=top style='width:261.95pt;border:solid #4F81BD 1.0pt;
 mso-border-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 size_type copy(charT* buf, size_type n, size_type
- pos = 0)<o:p></o:p>
+ style='mso-ansi-language:EN'>size_type copy(charT* buf, size_type n,
+ size_type pos = 0)<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;
@@ -17145,8 +17136,8 @@
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
 size_type
 string_find_(container, s, pos)<o:p></o:p>
- size_type string_find_(container,
- s)<o:p></o:p>
+ size_type
+ string_find_(container, s)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -17180,8 +17171,8 @@
 EN'>size_type rfind(charT* s, size_type pos, size_type n)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- size_type string_rfind_(container,
- s, pos, n)<o:p></o:p>
+ size_type
+ string_rfind_(container, s, pos, n)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -17288,8 +17279,8 @@
 EN'>size_type find_first_of (const string& s, size_type pos=0)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- size_type
- find_first_of_(container, s, pos)<o:p></o:p>
+ size_type find_first_of_(container,
+ s, pos)<o:p></o:p>
 size_type
 find_first_of_(container, s)<o:p></o:p>
 </td>
@@ -17302,7 +17293,8 @@
 <td width=437 valign=top style='width:261.95pt;border:solid #4F81BD 1.0pt;
 mso-border-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 size_type find_first_of (charT c, size_type pos=0)<o:p></o:p>
+ style='mso-ansi-language:EN'>size_type find_first_of (charT c, size_type
+ pos=0)<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;
@@ -17361,8 +17353,8 @@
 EN'>size_type find_first_not_of (const string& s, size_type pos=0)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- size_type find_first_not_of_(container,
- s, pos)<o:p></o:p>
+ size_type
+ find_first_not_of_(container, s, pos)<o:p></o:p>
 size_type
 find_first_not_of_(container, s)<o:p></o:p>
 </td>
@@ -17399,8 +17391,8 @@
 EN'>size_type find_last_of(charT* s, size_type pos, size_type n)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- size_type
- find_last_of_(container, s, pos, n)<o:p></o:p>
+ size_type find_last_of_(container,
+ s, pos, n)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -17485,8 +17477,7 @@
 <td width=437 valign=top style='width:261.95pt;border:solid #4F81BD 1.0pt;
 mso-border-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 size_type find_last_not_of (charT* s, size_type
- pos=npos)<o:p></o:p>
+ style='mso-ansi-language:EN'>size_type find_last_not_of (charT* s, size_type pos=npos)<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;
@@ -17511,8 +17502,8 @@
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
 size_type
 find_last_not_of_(container, s, pos)<o:p></o:p>
- size_type
- find_last_not_of_(container, s)<o:p></o:p>
+ size_type find_last_not_of_(container,
+ s)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -17580,13 +17571,13 @@
lang=EN-US style='mso-ansi-language:EN-US'><o:p> </o:p>

EUML provides two macros (sorry about
-that) to convert a function or method into a eUML-compatible functor for use in
-action / guard declarations.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>EUML provides two macros (sorry
+about that) to convert a function or method into a eUML-compatible functor for
+use in action / guard declarations.<o:p></o:p>

Let’s suppose we wrote a
-function printing the typeid of its parameter:<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>Let’s suppose we wrote a function
+printing the typeid of its parameter:<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'><span lang=EN-US
@@ -17708,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;
@@ -17799,8 +17790,8 @@

We now have a way to bind a method
-of an event, state or state machine or a simple function with a nicer syntax
-than a normal bind.<o:p></o:p>
+of an event, state or state machine or a simple function with a nicer syntax than
+a normal bind.<o:p></o:p>

<o:p> </o:p>
@@ -17898,13 +17889,14 @@

The same simple
-and composite state machines are implemented with
-Msm2 with standard frontend, the simple one also with eUML.<o:p></o:p>
+and composite state machines are implemented
+with Msm2 with standard frontend, the simple one also with <a
+href="EumlSimple.cpp">eUML</a>.<o:p></o:p>

As these simple machines need no
-terminate/interrupt states, no message queue and have no-throw guarantee on
-their actions, the Msm state machines are defined with minimum functionality.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>As these simple machines need no terminate/interrupt
+states, no message queue and have no-throw guarantee on their actions, the Msm
+state machines are defined with minimum functionality.<o:p></o:p>

VC9:<o:p></o:p>
@@ -17931,8 +17923,8 @@
Symbol;mso-bidi-font-family:Symbol;mso-ansi-language:EN-US'>·       
<![endif]>The
-fastest version is with eUML. It completes 47 times faster than Boost.Statechart.
-A transition costs on my Q6600 9ns.<o:p></o:p>
+fastest version is with eUML. It completes 47 times faster than
+Boost.Statechart. A transition costs on my Q6600 9ns.<o:p></o:p>

gcc 4.2.3:<o:p></o:p>
@@ -17976,11 +17968,11 @@

With g++ 4.3, it strongly depends on
-the compiler option (much more than VC). A good size state machine with –O3
-can generate an executable of 600kB, and with eUML you can get to 1.5MB. Now,
-trying with –Os –s I come down to 18kB and 30kB for the test state
-machines, while eUML will go down to 1MB (which is still big), so in this case
-eUML does not come for free.<o:p></o:p>
+the compiler option (much more than VC). A good size state machine with
+–O3 can generate an executable of 600kB, and with eUML you can get to 1.5MB.
+Now, trying with –Os –s I come down to 18kB and 30kB for the test
+state machines, while eUML will go down to 1MB (which is still big), so in this
+case eUML does not come for free.<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="_Compilers"></a>Compilers<o:p></o:p></h1>
@@ -18158,9 +18150,9 @@
Symbol;mso-ansi-language:EN-US'>·       <![endif]>Typeof: While g++ and VC9 compile
-“standard” state machines in comparable times, Typeof (while in both
-ways natively supported) seems to behave in a quadratic complexity with VC9 and
-VC10.<o:p></o:p>
+“standard” state machines in comparable times, Typeof (while in
+both ways natively supported) seems to behave in a quadratic complexity with
+VC9 and VC10.<o:p></o:p>

g++ 4.xQuestion: on_entry gets as argument, the sent event. What
-event do I get when the state becomes default-activated (because it is an
+style='mso-ansi-language:EN-US'>: on_entry gets as argument, the sent event.
+What event do I get when the state becomes default-activated (because it is an
initial state)?<o:p></o:p>

As you see, it is quite simple. You
-only need define an instance of Alarm in each zone. To add a new alarm is as simple
-as adding a new instance. The Alarm submachine is simply defined as:<o:p></o:p>
+only need define an instance of Alarm in each zone. To add a new alarm is as
+simple as adding a new instance. The Alarm submachine is simply defined as:<o:p></o:p>

<!--[if gte vml 1]><v:shape id="Grafik_x0020_6"
@@ -18668,10 +18660,11 @@
lang=EN-US style='font-family:"Courier New";mso-ansi-language:EN-US'><o:p> </o:p>

And identify each instance
-in alarmBeeps as Alarm<1>, Alarm<2>, etc.<o:p></o:p>
+lang=EN-US style='color:black;mso-ansi-language:EN-US'>And identify each
+instance in alarmBeeps as Alarm<1>, Alarm<2>,
+etc.<o:p></o:p>

<o:p> </o:p>
@@ -18798,8 +18791,8 @@
lang=EN-US style='mso-ansi-language:EN-US'><o:p> </o:p>

The following UML diagram shows how a
-UML designer might want to solve the problem (note, in UML, guards are
+lang=EN-US style='mso-ansi-language:EN-US'>The following UML diagram shows how
+a UML designer might want to solve the problem (note, in UML, guards are
surrounded by “[ ]” and actions follow a “ / “):<o:p></o:p>

Foreach sends one OneSong event for every song of the song list.
-If event for every song of the song
+list. If StringFind finds
the user-provided letters in the song, it sends a Found                                           
-process2_(OneSong(),                                    
+       process2_(OneSong(),*(State_<m_src_it>()++)) ),<o:p></o:p>

@@ -19206,8 +19201,8 @@
lang=EN-US style='mso-ansi-language:EN-US'><o:p> </o:p>

We define one attribute in Foreach,
-an iterator on the Input list. <o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>We define one attribute in Foreach, an
+iterator on the Input list. <o:p></o:p>

Entry:<o:p></o:p>
@@ -19225,14 +19220,13 @@

   Fsm_ refers to the current state
-machine containing Input and Result lists.<o:p></o:p>
+style='mso-spacerun:yes'>   Fsm_ refers to the current state machine
+containing Input and Result lists.<o:p></o:p>

      Fsm_<m_src_container>
-refers to the Input list.<o:p></o:p>
+style='mso-spacerun:yes'>     
+Fsm_<m_src_container> refers to the Input list.<o:p></o:p>

                                
-NoAction(), <o:p></o:p>
+style='mso-spacerun:yes'>                         
+       NoAction(), <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_ << string()/*m_letters*/ )) <o:p></o:p>
+style='mso-spacerun:yes'>                                
+attributes_ << string()/*m_letters*/
+)) <o:p></o:p>

<span
lang=EN-US style='font-size:10.0pt;font-family:"Courier New";mso-fareast-font-family:
@@ -19485,8 +19480,8 @@
<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>

@@ -19494,10 +19489,8 @@
mso-layout-grid-align:none;text-autospace:none'>         
-      ) ) ) transition_table;<o:p></o:p>
+style='mso-spacerun:yes'>               
+) ) ) transition_table;<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'>               
-                NoAction(), // Exit<o:p></o:p>
+style='mso-spacerun:yes'>                               
+NoAction(), //
+Exit<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'>                                           
-<< vector<OneSong>() /*m_tgt_container*/,
-// result<o:p></o:p>
+style='mso-spacerun:yes'>                      
+                     <<
+vector<OneSong>()
+/*m_tgt_container*/, //
+result<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'>                         
-      flags_<< no_flags_,<o:p></o:p>
+style='mso-spacerun:yes'>                               
+flags_<< no_flags_,<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'>Annex A Debugging<o:p></o:p></h1>

Normally, one does not need to know the
-ids generated for all the states of a state machine, unless for debugging
+lang=EN-US style='mso-ansi-language:EN-US'>Normally, one does not need to know
+the ids generated for all the states of a state machine, unless for debugging
purposes, like the pstate function does in the tutorials in order to display the name of the
@@ -19686,11 +19680,11 @@

What would you need for a coverage
-tool? You'd probably need to know how many states are defined in the state machine,
-and how many events can be fired. This way you could log the fired events and
-the states visited in the life of a concrete machine and be able to perform
-some coverage analysis, like “fired 65% of all possible events and
-visited 80% of the states defined in the state machine”.<o:p></o:p>
+tool? You'd probably need to know how many states are defined in the state
+machine, and how many events can be fired. This way you could log the fired
+events and the states visited in the life of a concrete machine and be able to
+perform some coverage analysis, like “fired 65% of all possible events
+and visited 80% of the states defined in the state machine”.<o:p></o:p>

To achieve this, Msm provides a few

Next message: christophe.j.henry_at_[hidden]: "[Boost-commit] svn:boost r57823 - in sandbox/msm/libs/msm/doc: . index-Dateien"
Previous message: christophe.j.henry_at_[hidden]: "[Boost-commit] svn:boost r57821 - sandbox/msm/boost/msm/front/euml"

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