Boost-Commit :

Date view	Thread view	Subject view	Author view

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

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

Log:
added note about functors inside a submachine.
Binary files modified:
   sandbox/msm/libs/msm/doc/index-Dateien/image027.jpg
Text files modified:
   sandbox/msm/libs/msm/doc/index-Dateien/filelist.xml | 26
   sandbox/msm/libs/msm/doc/index-Dateien/props0033.xml | 2
   sandbox/msm/libs/msm/doc/index.htm | 635 ++++++++++++++++++++-------------------
   3 files changed, 339 insertions(+), 324 deletions(-)

Modified: sandbox/msm/libs/msm/doc/index-Dateien/filelist.xml
==============================================================================
--- sandbox/msm/libs/msm/doc/index-Dateien/filelist.xml (original)
+++ sandbox/msm/libs/msm/doc/index-Dateien/filelist.xml 2009-11-20 15:57:15 EST (Fri, 20 Nov 2009)
@@ -5,30 +5,30 @@
 <o:File HRef="themedata.thmx"/>
 <o:File HRef="colorschememapping.xml"/>
 <o:File HRef="image001.jpg"/>
- <o:File HRef="image002.jpg"/>
+ <o:File HRef="image027.jpg"/>
 <o:File HRef="image003.jpg"/>
- <o:File HRef="image004.jpg"/>
+ <o:File HRef="image028.jpg"/>
 <o:File HRef="image005.jpg"/>
- <o:File HRef="image006.jpg"/>
+ <o:File HRef="image029.jpg"/>
 <o:File HRef="image007.jpg"/>
- <o:File HRef="image008.jpg"/>
+ <o:File HRef="image030.jpg"/>
 <o:File HRef="image009.jpg"/>
- <o:File HRef="image010.jpg"/>
+ <o:File HRef="image031.jpg"/>
 <o:File HRef="image011.jpg"/>
- <o:File HRef="image012.jpg"/>
+ <o:File HRef="image032.jpg"/>
 <o:File HRef="image013.jpg"/>
- <o:File HRef="image014.jpg"/>
+ <o:File HRef="image033.jpg"/>
 <o:File HRef="image015.jpg"/>
- <o:File HRef="image016.jpg"/>
+ <o:File HRef="image034.jpg"/>
 <o:File HRef="image017.jpg"/>
- <o:File HRef="image018.jpg"/>
+ <o:File HRef="image035.jpg"/>
 <o:File HRef="image019.jpg"/>
- <o:File HRef="image020.jpg"/>
+ <o:File HRef="image036.jpg"/>
 <o:File HRef="image021.jpg"/>
- <o:File HRef="image022.jpg"/>
+ <o:File HRef="image037.jpg"/>
 <o:File HRef="image023.jpg"/>
- <o:File HRef="image024.jpg"/>
+ <o:File HRef="image038.jpg"/>
 <o:File HRef="image025.jpg"/>
- <o:File HRef="image026.jpg"/>
+ <o:File HRef="image039.jpg"/>
 <o:File HRef="filelist.xml"/>
</xml>
\ No newline at end of file

Modified: sandbox/msm/libs/msm/doc/index-Dateien/image027.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-20 15:57:15 EST (Fri, 20 Nov 2009)
@@ -1,2 +1,2 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<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
+<ds:datastoreItem ds:itemID="{EF9B35B7-C726-456D-8F63-9097CA52530F}" 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:57:15 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>283</o:Revision>
+ <o:Revision>284</o:Revision>
 <o:Created>2009-09-03T20:17:00Z</o:Created>
- <o:LastSaved>2009-11-20T20:29:00Z</o:LastSaved>
+ <o:LastSaved>2009-11-20T20:55:00Z</o:LastSaved>
 <o:Pages>39</o:Pages>
- <o:Words>18955</o:Words>
- <o:Characters>119422</o:Characters>
- <o:Lines>995</o:Lines>
+ <o:Words>18988</o:Words>
+ <o:Characters>119628</o:Characters>
+ <o:Lines>996</o:Lines>
 <o:Paragraphs>276</o:Paragraphs>
- <o:CharactersWithSpaces>138101</o:CharactersWithSpaces>
+ <o:CharactersWithSpaces>138340</o:CharactersWithSpaces>
 <o:Version>12.00</o:Version>
 </o:DocumentProperties>
</xml><![endif]-->
@@ -4999,7 +4999,7 @@
<meta name=CHANGEDBY content=xtoff>
<meta name=CHANGEDBY content=xtoff>
<![if !vml]><img border=0 width=202 height=96
-src="index-Dateien/image002.jpg" alt=Transition.jpg v:shapes="Grafik_x0020_16"><![endif]><![endif]><o:p></o:p>

Where
@@ -5817,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>
@@ -6552,16 +6552,15 @@

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 !vml]><img border=0 width=600 height=581
-src="index-Dateien/image004.jpg" alt=SimpleTutorial.jpg v:shapes="Grafik_x0020_15"><![endif]><![endif]> 
<o:p></o:p>
@@ -6766,8 +6765,8 @@
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>

states are now classes/structs</code><code> </code><code>so
-they can have data. The states get default-constructed at initialization time.</code>so they
+can have data. The states get default-constructed at initialization time.</code><o:p></o:p>


 <v:imagedata src="index-Dateien/image005.jpg" o:title="CompositeTutorial"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=616 height=827
-src="index-Dateien/image006.jpg" alt=CompositeTutorial.jpg v:shapes="Grafik_x0020_14"><![endif]><![endif]> 
<o:p></o:p>
@@ -7181,9 +7180,9 @@
<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
@@ -7216,9 +7215,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>
@@ -7261,7 +7260,7 @@
 style='width:486.6pt;height:604.2pt;visibility:visible;mso-wrap-style:square'>
 <v:imagedata src="index-Dateien/image007.jpg" o:title="Orthogonal-deferred"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=649 height=806
-src="index-Dateien/image008.jpg" alt=Orthogonal-deferred.jpg v:shapes="Bild_x0020_4"><![endif]><![endif]> 
<o:p></o:p>
@@ -7330,8 +7329,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>

@@ -7440,16 +7439,16 @@
 style='width:427.2pt;height:617.4pt;visibility:visible;mso-wrap-style:square'>
 <v:imagedata src="index-Dateien/image009.jpg" o:title="HistoryTutorial"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=570 height=823
-src="index-Dateien/image010.jpg" alt=HistoryTutorial.jpg v:shapes="Grafik_x0020_12"><![endif]><![endif]> 
<o:p></o:p>

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>
@@ -7492,8 +7491,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 play</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>
@@ -7663,7 +7662,7 @@
 height:655.2pt;visibility:visible;mso-wrap-style:square'>
 <v:imagedata src="index-Dateien/image011.jpg" o:title="FlagsTutorial"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=616 height=874
-src="index-Dateien/image012.jpg" alt=FlagsTutorial.jpg v:shapes="Grafik_x0020_11"><![endif]><![endif]> 
<o:p></o:p>
@@ -7687,7 +7686,7 @@
 height:331.8pt;visibility:visible;mso-wrap-style:square'>
 <v:imagedata src="index-Dateien/image013.jpg" o:title="Anonymous"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=444 height=442
-src="index-Dateien/image014.jpg" alt=Anonymous.jpg v:shapes="Grafik_x0020_13"><![endif]><![endif]><o:p></o:p>

·       
<![endif]>Explicit entry:
-if a transition goes to a sub-state of a composite state, this state becomes
-active and like in the previous examples, its entry action is executed after
-the entry action from the composite state.<o:p></o:p>
+if a transition goes to a sub-state of a composite state, this state becomes active
+and like in the previous examples, its entry action is executed after the entry
+action from the composite state.<o:p></o:p>

<![if !supportLists]>
 <v:imagedata src="index-Dateien/image015.jpg" o:title="entry tutorial"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=634 height=766
-src="index-Dateien/image016.jpg" alt="entry tutorial.jpg" v:shapes="Grafik_x0020_10"><![endif]><![endif]> 
<o:p></o:p>
@@ -8253,9 +8252,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>
@@ -8294,9 +8293,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>
@@ -8452,8 +8451,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>

<span
@@ -8461,11 +8460,11 @@

Important note 2: UML defines transiting to an exit
-pseudo state and having no second transition as an error, and also defines no
-error handling. Therefore, it was decided to implement exit pseudo state as
-terminate states and the containing composite not properly exited will stay
-terminated as it was technically “exited”.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'> UML defines transiting to an exit pseudo
+state and having no second transition as an error, and also defines no error
+handling. Therefore, it was decided to implement exit pseudo state as terminate
+states and the containing composite not properly exited will stay terminated as
+it was technically “exited”.<o:p></o:p>

<o:p> </o:p>
@@ -8541,9 +8540,9 @@

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,
@@ -8708,8 +8707,8 @@
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>
+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;
@@ -8767,8 +8766,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:
@@ -8828,16 +8827,16 @@

<code>Normally, you
-should not need exceptions. UML also says little about exceptions. To handle
-errors, the best UML-safe method is to add an orthogonal region, like
-previously shown.</code><o:p></o:p>
+font-family:"Times New Roman","serif";mso-ansi-language:EN-US'>Normally, you should
+not need exceptions. UML also says little about exceptions. To handle errors,
+the best UML-safe method is to add an orthogonal region, like previously shown.</code><o:p></o:p>

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

@@ -9000,9 +8999,9 @@
style='mso-list:Ignore'>·       
<![endif]><code>handling the message queue (for
-entry/exit/transition actions generating themselves events)</code><o:p></o:p>
+color:black;mso-ansi-language:EN-US'>handling the message queue (for entry/exit/transition
+actions generating themselves events)</code><o:p></o:p>

<![if !supportLists]>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
@@ -9162,9 +9161,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
@@ -9335,8 +9334,8 @@
style='mso-list:Ignore'>·       
<![endif]><code>Add the user-defined base state in the
-state machine frontend definition, as a second template argument, for example:</code>Add the user-defined base state in the state
+machine frontend definition, as a second template argument, for example:</code> 
<code>struct</code><code>state_machine::visit_current_states will cause accept to be called on the currently
-active states. Typically, you will also want to provide an empty default to be called on the currently active
+states. Typically, you will also want to provide an empty default accept in your base state in order in
order not to force all your states to implement <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="_New_Msm_v2.0"></a>New
-Msm v2.0 Features <o:p></o:p></h1>
+name="_New_Msm_v2.0"></a>New Msm
+v2.0 Features <o:p></o:p></h1>

This chapter will introduce the new
@@ -9756,8 +9755,8 @@

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>
+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>
@@ -9881,8 +9880,10 @@
mso-layout-grid-align:none;text-autospace:none'>                                                             
-,DummyGuard                                          
+                   ,DummyGuard         
>,<o:p></o:p>

@@ -9932,9 +9933,8 @@
style='mso-spacerun:yes'>   < Open    , open_close  , Empty   , close_drawer
-       ,    , close_drawer        , none                
>,<o:p></o:p>
@@ -10015,17 +10015,17 @@
lang=EN-US style='font-family:Symbol;mso-fareast-font-family:Symbol;mso-bidi-font-family:
Symbol;mso-ansi-language:EN-US'>·       <![endif]>You can mix new rows with the old
-g_row, a_row, etc.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>You can mix new rows with the old g_row,
+a_row, etc.<o:p></o:p>

<p class=MsoListParagraphCxSpMiddle 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]>·       <![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
@@ -10126,6 +10127,16 @@
<o:p> </o:p>

+Note: in case this action is referenced in the transition
+table of a state machine contained inside a top-level state machine, the “fsm”
+parameter refers to the lowest-level state machine (referencing this action),
+not the top-level one.<o:p></o:p>
+
+<o:p> </o:p>
+
What if we defined a functor
pre-incrementing an attribute in the source while another functor compares the
@@ -10147,8 +10158,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
@@ -10195,9 +10206,10 @@
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'><span lang=EN-US
@@ -10414,13 +10427,13 @@

UML defines guards
-between “[ ]” and actions after a “/”, so this is
-already more readable for UML designers. UML also allows designers to define
-several actions sequentially (our previous ActionSequenceActionSequence) 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
@@ -10532,8 +10545,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>
@@ -10554,8 +10567,8 @@
a state with entry/exit functors<o:p></o:p></h3>

It is also possible to use the same
-action grammar with state entry and exit actions:<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>It is also possible to use the same action
+grammar with state entry and exit actions:<o:p></o:p>

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";
@@ -10847,9 +10861,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
@@ -11314,10 +11328,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:
@@ -11917,8 +11931,9 @@

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>
@@ -12224,7 +12239,8 @@
<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
@@ -12990,8 +13006,7 @@
 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'>
@@ -13127,8 +13142,7 @@
 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;
@@ -13350,8 +13364,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>
@@ -13473,8 +13487,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;
@@ -13497,8 +13511,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";
@@ -13615,8 +13629,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;
@@ -13709,8 +13723,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;
@@ -13739,9 +13753,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";
@@ -13931,9 +13945,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;
@@ -14244,12 +14258,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
@@ -14310,8 +14324,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>
@@ -14372,14 +14386,15 @@
<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:
@@ -15514,8 +15530,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;
@@ -16266,8 +16282,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'>
@@ -16519,8 +16535,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'>
@@ -16590,8 +16606,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'>
@@ -16974,8 +16990,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;
@@ -16996,8 +17012,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'>
@@ -17031,8 +17047,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'>
@@ -17064,7 +17080,8 @@
 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'>
@@ -17075,8 +17092,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;
@@ -17136,8 +17153,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'>
@@ -17171,8 +17188,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'>
@@ -17279,8 +17296,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>
@@ -17293,8 +17310,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_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;
@@ -17353,8 +17369,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>
@@ -17391,8 +17407,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'>
@@ -17477,7 +17493,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_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;
@@ -17502,8 +17519,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'>
@@ -17571,13 +17588,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
@@ -17699,13 +17716,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;
@@ -17790,8 +17807,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>
@@ -17889,14 +17906,13 @@

The same simple
-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>
+and composite state machines are implemented with
+Msm2 with standard frontend, the simple one also with eUML.<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>
@@ -17923,8 +17939,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>
@@ -17969,10 +17985,10 @@
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>
+–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>
@@ -18125,11 +18141,11 @@
mso-ansi-language:EN-US'>submachine::exit_pt” ? Because “exit” will crash the compiler.
-“Exit” is
-not possible either because it will crash the compiler on one machine, but not
-on another (the compiler was installed from the same disk).<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>” will crash the compiler. “Exit” is not possible either
+because it will crash the compiler on one machine, but not on another (the
+compiler was installed from the same disk).<o:p></o:p>

<p style='margin-left:36.0pt;text-indent:-18.0pt;mso-list:l28 level1 lfo42;
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]>Question: Why do I get a compile error saying the
-compiler cannot convert to a function ...Fsm::*(some_event): Why do I get a compile error saying the compiler
+cannot convert to a function ...Fsm::*(some_event)?<o:p></o:p>

</o:p>

First, we notice that “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>
+lang=EN-US style='mso-ansi-language:EN-US'>First, we notice that
+“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>

<![if !supportLists]>Please keep in mind that these
-companies produce hundreds of slightly different products, which makes this quite
-a realistic scenario.<o:p></o:p>
+companies produce hundreds of slightly different products, which makes this
+quite a realistic scenario.<o:p></o:p>

What would be the result? New states
@@ -18595,7 +18612,7 @@
 height:388.8pt;visibility:visible;mso-wrap-style:square'>
 <v:imagedata src="index-Dateien/image017.jpg" o:title="clock"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=554 height=518
-src="index-Dateien/image018.jpg" alt=clock.jpg v:shapes="Grafik_x0020_5"><![endif]><![endif]> 
<o:p></o:p>
@@ -18605,8 +18622,8 @@

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 !vml]><img border=0 width=467 height=306
-src="index-Dateien/image020.jpg" alt=alarm.jpg v:shapes="Grafik_x0020_6"><![endif]><![endif]> 
<o:p></o:p>
@@ -18660,11 +18677,10 @@
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>
@@ -18791,8 +18807,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>


 <v:imagedata src="index-Dateien/image021.jpg" o:title="Timer"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=594 height=628
-src="index-Dateien/image022.jpg" alt=Timer.jpg v:shapes="Grafik_x0020_7"><![endif]><![endif]><o:p></o:p>


 <v:imagedata src="index-Dateien/image023.jpg" o:title="iPodSearch"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=308 height=267
-src="index-Dateien/image024.jpg" alt=iPodSearch.jpg v:shapes="Grafik_x0020_8"><![endif]><![endif]><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>

@@ -19201,8 +19215,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>
@@ -19220,13 +19234,14 @@

   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:
@@ -19480,8 +19494,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>

@@ -19489,8 +19503,10 @@
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
@@ -19613,7 +19628,7 @@
 height:384.6pt;visibility:visible;mso-wrap-style:square'>
 <v:imagedata src="index-Dateien/image025.jpg" o:title="AnnexA"/>
</v:shape><![endif]--><![if !vml]><img border=0 width=798 height=513
-src="index-Dateien/image026.jpg" alt=AnnexA.jpg v:shapes="Grafik_x0020_9"><![endif]><![endif]> 
<o:p></o:p>
@@ -19680,11 +19695,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

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