Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r58021 - in sandbox/msm/libs/msm/doc: . index-Dateien
From: christophe.j.henry_at_[hidden]
Date: 2009-11-28 17:21:44

Next message: erwann.rogard_at_[hidden]: "[Boost-commit] svn:boost r58022 - sandbox/statistics/distribution_common/boost/statistics/detail/distribution_common/fwd"
Previous message: ramey_at_[hidden]: "[Boost-commit] svn:boost r58020 - trunk/libs/serialization/src"

Author: chenry
Date: 2009-11-28 17:21:43 EST (Sat, 28 Nov 2009)
New Revision: 58021
URL: http://svn.boost.org/trac/boost/changeset/58021

Log:
corrected wrong functor definition.
Text files modified:
   sandbox/msm/libs/msm/doc/index-Dateien/props0033.xml | 2
   sandbox/msm/libs/msm/doc/index.htm | 612 ++++++++++++++++++++-------------------
   2 files changed, 318 insertions(+), 296 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-28 17:21:43 EST (Sat, 28 Nov 2009)
@@ -1,2 +1,2 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<ds:datastoreItem ds:itemID="{71C8A8FF-8655-41FC-BBE6-6F3DF98D15B1}" 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="{4942D4C4-4300-40B2-8CF2-0485B273D346}" 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-28 17:21:43 EST (Sat, 28 Nov 2009)
@@ -23,15 +23,15 @@
 <o:Author>Christophe</o:Author>
 <o:Template>Normal</o:Template>
 <o:LastAuthor>Christophe</o:LastAuthor>
- <o:Revision>285</o:Revision>
+ <o:Revision>287</o:Revision>
 <o:Created>2009-09-03T20:17:00Z</o:Created>
- <o:LastSaved>2009-11-27T21:27:00Z</o:LastSaved>
+ <o:LastSaved>2009-11-28T22:21:00Z</o:LastSaved>
 <o:Pages>39</o:Pages>
 <o:Words>19068</o:Words>
- <o:Characters>120131</o:Characters>
+ <o:Characters>120129</o:Characters>
 <o:Lines>1001</o:Lines>
 <o:Paragraphs>277</o:Paragraphs>
- <o:CharactersWithSpaces>138922</o:CharactersWithSpaces>
+ <o:CharactersWithSpaces>138920</o:CharactersWithSpaces>
 <o:Version>12.00</o:Version>
 </o:DocumentProperties>
</xml><![endif]-->
@@ -449,65 +449,73 @@
 panose-1:2 2 6 9 4 2 5 8 3 4;
 mso-font-alt:"\FF2D\FF33 \660E\671D";
 mso-font-charset:128;
- mso-generic-font-family:modern;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:fixed;
- mso-font-signature:-536870145 1791491579 18 0 131231 0;}
+ mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
 {font-family:Batang;
 panose-1:2 3 6 0 0 1 1 1 1 1;
 mso-font-alt:\BC14\D0D5;
 mso-font-charset:129;
- mso-generic-font-family:roman;
- mso-font-pitch:variable;
- mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
+ mso-generic-font-family:auto;
+ mso-font-format:other;
+ mso-font-pitch:fixed;
+ mso-font-signature:1 151388160 16 0 524288 0;}
@font-face
 {font-family:SimSun;
 panose-1:2 1 6 0 3 1 1 1 1 1;
 mso-font-alt:\5B8B\4F53;
 mso-font-charset:134;
 mso-generic-font-family:auto;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:3 680460288 22 0 262145 0;}
+ mso-font-signature:1 135135232 16 0 262144 0;}
@font-face
 {font-family:PMingLiU;
 panose-1:2 2 5 0 0 0 0 0 0 0;
 mso-font-alt:\65B0\7D30\660E\9AD4;
 mso-font-charset:136;
- mso-generic-font-family:roman;
+ mso-generic-font-family:auto;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-1610611969 684719354 22 0 1048577 0;}
+ mso-font-signature:1 134742016 16 0 1048576 0;}
@font-face
 {font-family:"MS Gothic";
 panose-1:2 11 6 9 7 2 5 8 2 4;
 mso-font-alt:"\FF2D\FF33 \30B4\30B7\30C3\30AF";
 mso-font-charset:128;
 mso-generic-font-family:modern;
+ mso-font-format:other;
 mso-font-pitch:fixed;
- mso-font-signature:-536870145 1791491579 18 0 131231 0;}
+ mso-font-signature:1 134676480 16 0 131072 0;}
@font-face
 {font-family:Dotum;
 panose-1:2 11 6 0 0 1 1 1 1 1;
 mso-font-alt:\B3CB\C6C0;
 mso-font-charset:129;
- mso-generic-font-family:swiss;
- mso-font-pitch:variable;
- mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
+ mso-generic-font-family:modern;
+ mso-font-format:other;
+ mso-font-pitch:fixed;
+ mso-font-signature:1 151388160 16 0 524288 0;}
@font-face
 {font-family:SimHei;
 panose-1:2 1 6 9 6 1 1 1 1 1;
 mso-font-alt:\9ED1\4F53;
 mso-font-charset:134;
 mso-generic-font-family:modern;
+ mso-font-format:other;
 mso-font-pitch:fixed;
- mso-font-signature:-2147482945 953122042 22 0 262145 0;}
+ mso-font-signature:1 135135232 16 0 262144 0;}
@font-face
 {font-family:MingLiU;
 panose-1:2 2 5 9 0 0 0 0 0 0;
 mso-font-alt:\7D30\660E\9AD4;
 mso-font-charset:136;
 mso-generic-font-family:modern;
+ mso-font-format:other;
 mso-font-pitch:fixed;
- mso-font-signature:-1610611969 684719354 22 0 1048577 0;}
+ mso-font-signature:1 134742016 16 0 1048576 0;}
@font-face
 {font-family:Mincho;
 panose-1:2 2 6 9 4 3 5 8 3 5;
@@ -522,37 +530,42 @@
 panose-1:2 11 6 0 0 1 1 1 1 1;
 mso-font-alt:\AD74\B9BC;
 mso-font-charset:129;
- mso-generic-font-family:swiss;
- mso-font-pitch:variable;
- mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
+ mso-generic-font-family:roman;
+ mso-font-format:other;
+ mso-font-pitch:fixed;
+ mso-font-signature:1 151388160 16 0 524288 0;}
@font-face
 {font-family:Century;
 panose-1:2 4 6 4 5 5 5 2 3 4;
 mso-font-charset:0;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:647 0 0 0 159 0;}
+ mso-font-signature:3 0 0 0 1 0;}
@font-face
 {font-family:"Angsana New";
 panose-1:2 2 6 3 5 4 5 2 3 4;
- mso-font-charset:0;
+ mso-font-charset:222;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-2130706429 0 0 0 65537 0;}
+ mso-font-signature:16777217 0 0 0 65536 0;}
@font-face
 {font-family:"Cordia New";
 panose-1:2 11 3 4 2 2 2 2 2 4;
- mso-font-charset:0;
- mso-generic-font-family:swiss;
+ mso-font-charset:222;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-2130706429 0 0 0 65537 0;}
+ mso-font-signature:16777217 0 0 0 65536 0;}
@font-face
 {font-family:Mangal;
 panose-1:2 4 5 3 5 2 3 3 2 2;
- mso-font-charset:0;
+ mso-font-charset:1;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:32771 0 0 0 1 0;}
+ mso-font-signature:8192 0 0 0 0 0;}
@font-face
 {font-family:Latha;
 panose-1:2 0 4 0 0 0 0 0 0 0;
@@ -566,29 +579,33 @@
 panose-1:1 10 5 2 5 3 6 3 3 3;
 mso-font-charset:0;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:67110535 0 0 0 159 0;}
+ mso-font-signature:12583555 0 0 0 13 0;}
@font-face
 {font-family:Vrinda;
 panose-1:1 1 6 0 1 1 1 1 1 1;
- mso-font-charset:0;
- mso-generic-font-family:auto;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:65539 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:Raavi;
 panose-1:2 0 5 0 0 0 0 0 0 0;
- mso-font-charset:0;
- mso-generic-font-family:auto;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:131075 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:Shruti;
 panose-1:2 11 6 4 2 2 2 2 2 4;
- mso-font-charset:0;
- mso-generic-font-family:swiss;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:262147 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:Sendnya;
 panose-1:0 0 4 0 0 0 0 0 0 0;
@@ -600,38 +617,43 @@
@font-face
 {font-family:Gautami;
 panose-1:2 0 5 0 0 0 0 0 0 0;
- mso-font-charset:0;
- mso-generic-font-family:auto;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-2145386493 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:Tunga;
 panose-1:0 0 4 0 0 0 0 0 0 0;
- mso-font-charset:0;
- mso-generic-font-family:auto;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:4194307 0 0 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:"Estrangelo Edessa";
 panose-1:3 8 6 0 0 0 0 0 0 0;
- mso-font-charset:0;
- mso-generic-font-family:script;
+ mso-font-charset:1;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-2147475389 0 128 0 1 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:"Cambria Math";
 panose-1:2 4 5 3 5 4 6 3 2 4;
- mso-font-charset:0;
+ mso-font-charset:1;
 mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-1610611985 1107304683 0 0 159 0;}
+ mso-font-signature:0 0 0 0 0 0;}
@font-face
 {font-family:"Arial Unicode MS";
 panose-1:2 11 6 4 2 2 2 2 2 4;
- mso-font-charset:128;
- mso-generic-font-family:swiss;
+ mso-font-charset:0;
+ mso-generic-font-family:roman;
+ mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:-134238209 -371195905 63 0 4129279 0;}
+ mso-font-signature:3 0 0 0 1 0;}
@font-face
 {font-family:Cambria;
 panose-1:2 4 5 3 5 4 6 3 2 4;
@@ -4977,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"/>
@@ -5795,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>
@@ -6530,9 +6552,8 @@

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"
@@ -6744,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>

<p style='margin-top:5.0pt;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;
@@ -7683,12 +7704,12 @@

Another possible use would be a
-real-time system called at regular intervals and always doing the same thing, meaning
-implementing the same algorithm. The advantage is that once you know how long a
-transition takes to execute on the system, by calculating the longest path (the
-number of transitions from start to end), you can pretty much know how long
-your algorithm will take in the worst case, which in turns tells you how big of
-a time frame you are to request from a scheduler.<o:p></o:p>
+real-time system called at regular intervals and always doing the same thing,
+meaning implementing the same algorithm. The advantage is that once you know
+how long a transition takes to execute on the system, by calculating the
+longest path (the number of transitions from start to end), you can pretty much
+know how long your algorithm will take in the worst case, which in turns tells
+you how big of a time frame you are to request from a scheduler.<o:p></o:p>

What is the cost of this feature? If
@@ -7730,8 +7751,8 @@
style='color:#030003'>State3 
, none        , State4  , State3ToState4State4 
+, State3ToState4      , always_true         
@@ -7806,9 +7827,9 @@
style='mso-list:Ignore'>·       
<![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]><span lang=EN-US style='font-size:
@@ -8429,9 +8450,9 @@

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
+lang=EN-US style='mso-ansi-language:EN-US'> 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 will simply be the newly active state.<o:p></o:p>

<span
@@ -8439,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>
@@ -8519,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,
@@ -8686,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;
@@ -8745,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:
@@ -8806,10 +8827,10 @@

<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>·       
<![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]>·       <![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
@@ -9234,8 +9255,8 @@
lang=EN-US style='mso-ansi-language:EN-US'>By default, all states derive from msm::default_base_state, which is neither polymorphic nor
-has any other useful purpose than to define a base for all states. The following
-part will describe the customization possibilities offered by Msm.<o:p></o:p>
+has any other useful purpose than to define a base for all states. The
+following part will describe the customization possibilities offered by Msm.<o:p></o:p>

<h3 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_User-defined_base_state"></a><code>·       
<![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
@@ -9734,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>
@@ -9994,8 +10015,8 @@
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]>    void
-operator()(FSM&
-fsm,EVT const& ,SourceState&
+operator()(EVT
+const& ,FSM&
+fsm ,SourceState&
,TargetState& )<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;
@@ -10094,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
@@ -10196,11 +10216,11 @@
actions, guards, flags, attributes, deferred events, initial states.<o:p></o:p>

It also relies on Boost.Typeof
-as a wrapper around the new decltype C++0x feature to provide a compile-time
-evaluation of all the grammars. Unfortunately, all the underlying Boost
-libraries are not Typeof-enabled, so for the moment, you will need a compiler
-where Typeof is natively implemented (like VC8-9-10, g++ >= 4.3)<o:p></o:p>
+lang=EN-US style='color:black;mso-ansi-language:EN-US'>It also relies on
+Boost.Typeof as a wrapper around the new decltype C++0x feature to provide a
+compile-time evaluation of all the grammars. Unfortunately, all the underlying
+Boost libraries are not Typeof-enabled, so for the moment, you will need a
+compiler where Typeof is natively implemented (like VC8-9-10, g++ >= 4.3)<o:p></o:p>

To play with grammars,
@@ -10251,8 +10271,8 @@
lang=EN-US style='color:black;mso-ansi-language:EN-US'><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'>    bool
-operator()(FSM&
-,EVT const&
-evt,SourceState&
+operator()(EVT
+const& ,FSM& ,SourceState&
,TargetState& )<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;
@@ -10523,8 +10543,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>
@@ -10561,8 +10581,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 <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>

        //  +------------------------------------------------------------------------------+<o:p></o:p>
+style='color:green'>// 
++------------------------------------------------------------------------------+<o:p></o:p>

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

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

·       <![endif]>[(if_then_else_( True_(),Guard1(),Guard2()))]
-is a guard returning the result of
-calling Guard1 (True_ will, well, return true).<o:p></o:p>
+"Times New Roman";mso-ansi-language:EN-US;mso-no-proof:yes'>[(if_then_else_(
+True_(),Guard1(),Guard2()))] is a guard
+returning the result of calling Guard1 (True_ will, well,
+return true).<o:p></o:p>

<p style='margin-top:5.0pt;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;
margin-bottom:.0001pt;text-indent:-18.0pt;mso-list:l27 level1 lfo36;tab-stops:
@@ -12875,8 +12895,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
- / Action1--.<o:p></o:p>
+ mso-yfti-cnfc:64'>Calls lazily
+ --Action1 / 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;
@@ -13316,7 +13336,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'>
@@ -13342,8 +13363,9 @@
 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>
@@ -13511,8 +13533,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 some_int
- attribute of the target state from the currently triggered transition.<o:p></o:p>
+ mso-yfti-cnfc:64'>Returns the
+ some_int attribute of the target state from the currently triggered
+ 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;
@@ -13581,8 +13604,9 @@
 </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 current
- state machine (valid inside an entry/exit state action or a transition).<o:p></o:p>
+ lang=EN style='mso-ansi-language:EN'>Returns the some_int attribute of the
+ current state machine (valid inside an entry/exit state action or a
+ transition).<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
 ++attribute_(fsm_(),Int_<0>())<o:p></o:p>
 Preincrements the first attribute of the
- current state machine<o:p></o:p>
+ "Times New Roman";mso-ansi-language:EN'>Preincrements the first attribute of
+ the current state machine<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'>
@@ -14298,12 +14322,12 @@
lang=EN-US style='mso-ansi-language:EN-US'><o:p> </o:p>

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 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>
+lang=EN-US style='mso-ansi-language:EN-US'>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
+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>

The file structure of this
@@ -15505,8 +15529,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;
@@ -16257,8 +16281,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'>
@@ -16510,8 +16534,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'>
@@ -16581,8 +16605,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'>
@@ -16965,8 +16989,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;
@@ -16987,8 +17011,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'>
@@ -17022,8 +17046,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'>
@@ -17055,7 +17079,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'>
@@ -17066,8 +17091,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;
@@ -17127,8 +17152,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'>
@@ -17162,8 +17187,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'>
@@ -17270,8 +17295,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>
@@ -17284,8 +17309,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;
@@ -17344,8 +17368,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>
@@ -17382,8 +17406,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'>
@@ -17468,7 +17492,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;
@@ -17493,8 +17518,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'>
@@ -17562,13 +17587,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
@@ -17690,13 +17715,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;
@@ -17781,8 +17806,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>
@@ -17880,14 +17905,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>
@@ -17914,8 +17938,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>
@@ -17960,10 +17984,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>
@@ -18116,11 +18140,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]>·       <![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>

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

<h1 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
name="_EUML_Case_Studies"></a>eUML
@@ -18876,8 +18900,8 @@
lang=EN-US style='font-family:"Courier New";mso-ansi-language:EN-US'>Ringing, 2 transitions can handle the tick event. We therefore define 2
-mutually exclusive guards: the one moving back to event. We therefore define 2 mutually
+exclusive guards: the one moving back to Ringing is true if counter – tick
@@ -18889,10 +18913,10 @@
tick <= 0. <o:p></o:p>

Otherwise, if any button
-(start/stop) is pressed, we move back to Stopped.<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>Otherwise, if any button (start/stop)
+is pressed, we move back to Stopped.<o:p></o:p>

<o:p> </o:p>
@@ -18909,8 +18933,8 @@

With eUML, the code is equivalent to
-the model (and could be parsed back to the model if necessary). So let’s
-go back to what we wrote in the model and analyze the conversion:<o:p></o:p>
+the model (and could be parsed back to the model if necessary). So let’s go
+back to what we wrote in the model and analyze the conversion:<o:p></o:p>

<p class=MsoListParagraphCxSpFirst style='text-indent:-18.0pt;mso-list:l25 level1 lfo37;
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]>The previous example is a standard
-application for state machines. But we want to push our model-driven approach
-further by using a state machine to write an algorithm. I already see some at
-the back of the room looking perplexed. Well, why not? Usually, UML designers like
-to use Activity Diagrams to do this, but mostly for documentation purposes
-because Activity Diagrams are hard to define with a precision needed for
-automatic code generation. On the other hand, state machines have a very strict
-formalism which enables code generation while being “cousin” with
-Activity Diagrams.<o:p></o:p>
+application for state machines. But we want to push our model-driven approach further
+by using a state machine to write an algorithm. I already see some at the back
+of the room looking perplexed. Well, why not? Usually, UML designers like to
+use Activity Diagrams to do this, but mostly for documentation purposes because
+Activity Diagrams are hard to define with a precision needed for automatic code
+generation. On the other hand, state machines have a very strict formalism
+which enables code generation while being “cousin” with Activity
+Diagrams.<o:p></o:p>

Let’s suppose we are asked to
@@ -19046,8 +19070,8 @@
lang=EN-US style='mso-ansi-language:EN-US'><o:p> </o:p>

We now want to do this using a
-model-driven approach with state machines. I suggest the following machine:<o:p></o:p>
+lang=EN-US style='mso-ansi-language:EN-US'>We now want to do this using a model-driven
+approach with state machines. I suggest the following machine:<o:p></o:p>

<o:p> </o:p>
@@ -19184,10 +19208,8 @@
mso-layout-grid-align:none;text-autospace:none'>                                    
-       process2_(OneSong(),                                           
+process2_(OneSong(),*(State_<m_src_it>()++)) ),<o:p></o:p>

@@ -19195,8 +19217,10 @@
mso-layout-grid-align:none;text-autospace:none'>                                 
-NoAction(), <o:p></o:p>
+style='mso-spacerun:yes'>                     
+            NoAction(), <o:p></o:p>

<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>
@@ -19230,8 +19254,8 @@

   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>

                                                
-process2_(Found(),                                         
+       process2_(Found(),Event_<m_song>()),<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;
@@ -19311,10 +19337,8 @@
mso-layout-grid-align:none;text-autospace:none'>                         
-       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'><span lang=EN-US
@@ -19490,8 +19514,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>

@@ -19522,10 +19546,9 @@
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'>                               
-attributes_ << vector<OneSong>()
-/*m_src_container*/ //
-song list<o:p></o:p>
+style='mso-spacerun:yes'>                                attributes_ << vector<OneSong>() /*m_src_container*/
+// song list<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'>                               
-defer_ << no_defer_<o:p></o:p>
+style='mso-spacerun:yes'>                
+               defer_ << no_defer_<o:p></o:p>

</o:p>

If you have some implicitly created
-states, like transition-less initial states or states created using the If you have some implicitly created states,
+like transition-less initial states or states created using the explicit_creation typedef, these will be added as a
source at the end of the transition table.<o:p></o:p>

Next message: erwann.rogard_at_[hidden]: "[Boost-commit] svn:boost r58022 - sandbox/statistics/distribution_common/boost/statistics/detail/distribution_common/fwd"
Previous message: ramey_at_[hidden]: "[Boost-commit] svn:boost r58020 - trunk/libs/serialization/src"

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