Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r57983 - in sandbox/msm/libs/msm/doc: . index-Dateien
From: christophe.j.henry_at_[hidden]
Date: 2009-11-27 16:28:26

Next message: hartmut.kaiser_at_[hidden]: "[Boost-commit] svn:boost r57984 - trunk/libs/program_options/src"
Previous message: ramey_at_[hidden]: "[Boost-commit] svn:boost r57982 - in trunk/libs/serialization: doc src util vc7ide"

Author: chenry
Date: 2009-11-27 16:28:25 EST (Fri, 27 Nov 2009)
New Revision: 57983
URL: http://svn.boost.org/trac/boost/changeset/57983

Log:
added in doc a possible compiler error message.
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 | 737 +++++++++++++++++++--------------------
   3 files changed, 380 insertions(+), 385 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-27 16:28:25 EST (Fri, 27 Nov 2009)
@@ -5,30 +5,30 @@
 <o:File HRef="themedata.thmx"/>
 <o:File HRef="colorschememapping.xml"/>
 <o:File HRef="image001.jpg"/>
- <o:File HRef="image027.jpg"/>
+ <o:File HRef="image002.jpg"/>
 <o:File HRef="image003.jpg"/>
- <o:File HRef="image028.jpg"/>
+ <o:File HRef="image004.jpg"/>
 <o:File HRef="image005.jpg"/>
- <o:File HRef="image029.jpg"/>
+ <o:File HRef="image006.jpg"/>
 <o:File HRef="image007.jpg"/>
- <o:File HRef="image030.jpg"/>
+ <o:File HRef="image008.jpg"/>
 <o:File HRef="image009.jpg"/>
- <o:File HRef="image031.jpg"/>
+ <o:File HRef="image010.jpg"/>
 <o:File HRef="image011.jpg"/>
- <o:File HRef="image032.jpg"/>
+ <o:File HRef="image012.jpg"/>
 <o:File HRef="image013.jpg"/>
- <o:File HRef="image033.jpg"/>
+ <o:File HRef="image014.jpg"/>
 <o:File HRef="image015.jpg"/>
- <o:File HRef="image034.jpg"/>
+ <o:File HRef="image016.jpg"/>
 <o:File HRef="image017.jpg"/>
- <o:File HRef="image035.jpg"/>
+ <o:File HRef="image018.jpg"/>
 <o:File HRef="image019.jpg"/>
- <o:File HRef="image036.jpg"/>
+ <o:File HRef="image020.jpg"/>
 <o:File HRef="image021.jpg"/>
- <o:File HRef="image037.jpg"/>
+ <o:File HRef="image022.jpg"/>
 <o:File HRef="image023.jpg"/>
- <o:File HRef="image038.jpg"/>
+ <o:File HRef="image024.jpg"/>
 <o:File HRef="image025.jpg"/>
- <o:File HRef="image039.jpg"/>
+ <o:File HRef="image026.jpg"/>
 <o:File HRef="filelist.xml"/>
</xml>
\ No newline at end of file

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-27 16:28:25 EST (Fri, 27 Nov 2009)
@@ -1,2 +1,2 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<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
+<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

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-27 16:28:25 EST (Fri, 27 Nov 2009)
@@ -23,15 +23,15 @@
 <o:Author>Christophe</o:Author>
 <o:Template>Normal</o:Template>
 <o:LastAuthor>Christophe</o:LastAuthor>
- <o:Revision>284</o:Revision>
+ <o:Revision>285</o:Revision>
 <o:Created>2009-09-03T20:17:00Z</o:Created>
- <o:LastSaved>2009-11-20T20:55:00Z</o:LastSaved>
+ <o:LastSaved>2009-11-27T21:27:00Z</o:LastSaved>
 <o:Pages>39</o:Pages>
- <o:Words>18988</o:Words>
- <o:Characters>119628</o:Characters>
- <o:Lines>996</o:Lines>
- <o:Paragraphs>276</o:Paragraphs>
- <o:CharactersWithSpaces>138340</o:CharactersWithSpaces>
+ <o:Words>19068</o:Words>
+ <o:Characters>120131</o:Characters>
+ <o:Lines>1001</o:Lines>
+ <o:Paragraphs>277</o:Paragraphs>
+ <o:CharactersWithSpaces>138922</o:CharactersWithSpaces>
 <o:Version>12.00</o:Version>
 </o:DocumentProperties>
</xml><![endif]-->
@@ -449,73 +449,65 @@
 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:roman;
- mso-font-format:other;
+ mso-generic-font-family:modern;
 mso-font-pitch:fixed;
- mso-font-signature:1 134676480 16 0 131072 0;}
+ mso-font-signature:-536870145 1791491579 18 0 131231 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:auto;
- mso-font-format:other;
- mso-font-pitch:fixed;
- mso-font-signature:1 151388160 16 0 524288 0;}
+ mso-generic-font-family:roman;
+ mso-font-pitch:variable;
+ mso-font-signature:-1342176593 1775729915 48 0 524447 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:1 135135232 16 0 262144 0;}
+ mso-font-signature:3 680460288 22 0 262145 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:auto;
- mso-font-format:other;
+ mso-generic-font-family:roman;
 mso-font-pitch:variable;
- mso-font-signature:1 134742016 16 0 1048576 0;}
+ mso-font-signature:-1610611969 684719354 22 0 1048577 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:1 134676480 16 0 131072 0;}
+ mso-font-signature:-536870145 1791491579 18 0 131231 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:modern;
- mso-font-format:other;
- mso-font-pitch:fixed;
- mso-font-signature:1 151388160 16 0 524288 0;}
+ mso-generic-font-family:swiss;
+ mso-font-pitch:variable;
+ mso-font-signature:-1342176593 1775729915 48 0 524447 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:1 135135232 16 0 262144 0;}
+ mso-font-signature:-2147482945 953122042 22 0 262145 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:1 134742016 16 0 1048576 0;}
+ mso-font-signature:-1610611969 684719354 22 0 1048577 0;}
@font-face
 {font-family:Mincho;
 panose-1:2 2 6 9 4 3 5 8 3 5;
@@ -530,42 +522,37 @@
 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:roman;
- mso-font-format:other;
- mso-font-pitch:fixed;
- mso-font-signature:1 151388160 16 0 524288 0;}
+ mso-generic-font-family:swiss;
+ mso-font-pitch:variable;
+ mso-font-signature:-1342176593 1775729915 48 0 524447 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:3 0 0 0 1 0;}
+ mso-font-signature:647 0 0 0 159 0;}
@font-face
 {font-family:"Angsana New";
 panose-1:2 2 6 3 5 4 5 2 3 4;
- mso-font-charset:222;
+ mso-font-charset:0;
 mso-generic-font-family:roman;
- mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:16777217 0 0 0 65536 0;}
+ mso-font-signature:-2130706429 0 0 0 65537 0;}
@font-face
 {font-family:"Cordia New";
 panose-1:2 11 3 4 2 2 2 2 2 4;
- mso-font-charset:222;
- mso-generic-font-family:roman;
- mso-font-format:other;
+ mso-font-charset:0;
+ mso-generic-font-family:swiss;
 mso-font-pitch:variable;
- mso-font-signature:16777217 0 0 0 65536 0;}
+ mso-font-signature:-2130706429 0 0 0 65537 0;}
@font-face
 {font-family:Mangal;
 panose-1:2 4 5 3 5 2 3 3 2 2;
- mso-font-charset:1;
+ mso-font-charset:0;
 mso-generic-font-family:roman;
- mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:8192 0 0 0 0 0;}
+ mso-font-signature:32771 0 0 0 1 0;}
@font-face
 {font-family:Latha;
 panose-1:2 0 4 0 0 0 0 0 0 0;
@@ -579,33 +566,29 @@
 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:12583555 0 0 0 13 0;}
+ mso-font-signature:67110535 0 0 0 159 0;}
@font-face
 {font-family:Vrinda;
 panose-1:1 1 6 0 1 1 1 1 1 1;
- mso-font-charset:1;
- mso-generic-font-family:roman;
- mso-font-format:other;
+ mso-font-charset:0;
+ mso-generic-font-family:auto;
 mso-font-pitch:variable;
- mso-font-signature:0 0 0 0 0 0;}
+ mso-font-signature:65539 0 0 0 1 0;}
@font-face
 {font-family:Raavi;
 panose-1:2 0 5 0 0 0 0 0 0 0;
- mso-font-charset:1;
- mso-generic-font-family:roman;
- mso-font-format:other;
+ mso-font-charset:0;
+ mso-generic-font-family:auto;
 mso-font-pitch:variable;
- mso-font-signature:0 0 0 0 0 0;}
+ mso-font-signature:131075 0 0 0 1 0;}
@font-face
 {font-family:Shruti;
 panose-1:2 11 6 4 2 2 2 2 2 4;
- mso-font-charset:1;
- mso-generic-font-family:roman;
- mso-font-format:other;
+ mso-font-charset:0;
+ mso-generic-font-family:swiss;
 mso-font-pitch:variable;
- mso-font-signature:0 0 0 0 0 0;}
+ mso-font-signature:262147 0 0 0 1 0;}
@font-face
 {font-family:Sendnya;
 panose-1:0 0 4 0 0 0 0 0 0 0;
@@ -617,43 +600,38 @@
@font-face
 {font-family:Gautami;
 panose-1:2 0 5 0 0 0 0 0 0 0;
- mso-font-charset:1;
- mso-generic-font-family:roman;
- mso-font-format:other;
+ mso-font-charset:0;
+ mso-generic-font-family:auto;
 mso-font-pitch:variable;
- mso-font-signature:0 0 0 0 0 0;}
+ mso-font-signature:-2145386493 0 0 0 1 0;}
@font-face
 {font-family:Tunga;
 panose-1:0 0 4 0 0 0 0 0 0 0;
- mso-font-charset:1;
- mso-generic-font-family:roman;
- mso-font-format:other;
+ mso-font-charset:0;
+ mso-generic-font-family:auto;
 mso-font-pitch:variable;
- mso-font-signature:0 0 0 0 0 0;}
+ mso-font-signature:4194307 0 0 0 1 0;}
@font-face
 {font-family:"Estrangelo Edessa";
 panose-1:3 8 6 0 0 0 0 0 0 0;
- mso-font-charset:1;
- mso-generic-font-family:roman;
- mso-font-format:other;
+ mso-font-charset:0;
+ mso-generic-font-family:script;
 mso-font-pitch:variable;
- mso-font-signature:0 0 0 0 0 0;}
+ mso-font-signature:-2147475389 0 128 0 1 0;}
@font-face
 {font-family:"Cambria Math";
 panose-1:2 4 5 3 5 4 6 3 2 4;
- mso-font-charset:1;
+ mso-font-charset:0;
 mso-generic-font-family:roman;
- mso-font-format:other;
 mso-font-pitch:variable;
- mso-font-signature:0 0 0 0 0 0;}
+ mso-font-signature:-1610611985 1107304683 0 0 159 0;}
@font-face
 {font-family:"Arial Unicode MS";
 panose-1:2 11 6 4 2 2 2 2 2 4;
- mso-font-charset:0;
- mso-generic-font-family:roman;
- mso-font-format:other;
+ mso-font-charset:128;
+ mso-generic-font-family:swiss;
 mso-font-pitch:variable;
- mso-font-signature:3 0 0 0 1 0;}
+ mso-font-signature:-134238209 -371195905 63 0 4129279 0;}
@font-face
 {font-family:Cambria;
 panose-1:2 4 5 3 5 4 6 3 2 4;
@@ -4999,7 +4977,7 @@
<meta name=CHANGEDBY content=xtoff>
<meta name=CHANGEDBY content=xtoff>
<![if !vml]><img border=0 width=202 height=96
-src="index-Dateien/image027.jpg" alt=Transition.jpg v:shapes="Grafik_x0020_16"><![endif]><![endif]><o:p></o:p>

Where
@@ -5817,9 +5795,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,15 +6530,16 @@

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/image028.jpg" alt=SimpleTutorial.jpg v:shapes="Grafik_x0020_15"><![endif]><![endif]> 
<o:p></o:p>
@@ -6765,8 +6744,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/image029.jpg" alt=CompositeTutorial.jpg v:shapes="Grafik_x0020_14"><![endif]><![endif]> 
<o:p></o:p>
@@ -7260,7 +7239,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/image030.jpg" alt=Orthogonal-deferred.jpg v:shapes="Bild_x0020_4"><![endif]><![endif]> 
<o:p></o:p>
@@ -7439,7 +7418,7 @@
 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/image031.jpg" alt=HistoryTutorial.jpg v:shapes="Grafik_x0020_12"><![endif]><![endif]> 
<o:p></o:p>
@@ -7527,8 +7506,8 @@
itself useful on many occasions. Please, do not be frightened as we are not
talking about ugly shortcuts made of an improbable collusion of Booleans.<o:p></o:p>

-So what is it and what is
-its use?<o:p></o:p>
+So what is it and what is its
+use?<o:p></o:p>

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

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

<code>typedef</code><code>
 <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/image032.jpg" alt=FlagsTutorial.jpg v:shapes="Grafik_x0020_11"><![endif]><![endif]> 
<o:p></o:p>
@@ -7686,14 +7665,14 @@
 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/image033.jpg" alt=Anonymous.jpg v:shapes="Grafik_x0020_13"><![endif]><![endif]><o:p></o:p>

Anonymous transitions are
transitions without a named event. This means that the transition automatically
-fires when the predecessor state is entered (to be exact, after the entry
-condition). Otherwise it is a normal transition with actions and guards. <o:p></o:p>
+fires when the predecessor state is entered (to be exact, after the entry condition).
+Otherwise it is a normal transition with actions and guards. <o:p></o:p>

Why would you need something like
@@ -7704,12 +7683,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
@@ -7751,8 +7730,8 @@
style='color:#030003'>State3 
, none        , State4 
-, State3ToState4State4  , State3ToState4      , always_true         
@@ -7827,9 +7806,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]>
 <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/image034.jpg" alt="entry tutorial.jpg" v:shapes="Grafik_x0020_10"><![endif]><![endif]> 
<o:p></o:p>
@@ -8450,8 +8429,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
+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>

@@ -8460,11 +8439,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>
@@ -8540,9 +8519,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,
@@ -8707,8 +8686,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;
@@ -8766,8 +8745,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:
@@ -8827,10 +8806,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
@@ -9255,8 +9234,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
@@ -9755,8 +9734,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>
@@ -10015,8 +9994,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]>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>
+style='mso-ansi-language:EN-US'>: 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>
@@ -10217,11 +10196,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,
@@ -10396,8 +10375,7 @@
style='font-size:10.0pt;font-family:"Courier New";mso-fareast-font-family:"Times New Roman";
mso-ansi-language:EN-US;mso-no-proof:yes'>     // 
-+------------------------------------------------------------------------------+<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
@@ -10427,10 +10405,10 @@

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>
@@ -10545,8 +10523,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>
@@ -10567,8 +10545,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>

<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";
@@ -10861,9 +10839,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
@@ -11328,10 +11306,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>

              
-                  attributes_ << no_attributes_,<o:p></o:p>
+style='mso-spacerun:yes'>                                
+attributes_ << no_attributes_,<o:p></o:p>

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

@@ -12412,8 +12390,7 @@
style='font:7.0pt "Times New Roman"'>       <![endif]>String_<mpl::string>: Wrapper around std::string. Needs
-Boost >= 1.40. You can then define a string in an action, for example
-String_<mpl::string<’Hell’,’o
+Boost >= 1.40. You can then define a string in an action, for example String_<mpl::string<’Hell’,’o
wo’,’rld’> >(). Please refer to the <a
href="http://www.boost.org/doc/libs/1_40_0/libs/mpl/doc/refmanual/string.html">MPL
documentation</a>. This is the one case where you will see some
@@ -12495,14 +12472,14 @@
Symbol;mso-ansi-language:EN-US'>·       <![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>

</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
@@ -12898,8 +12875,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;
@@ -13006,7 +12983,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'>
@@ -13142,7 +13120,8 @@
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
 mso-border-bottom-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 <p style='margin-bottom:0cm;margin-bottom:.0001pt;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
- mso-yfti-cnfc:64'>Calls lazily -Action1<o:p></o:p>
+ mso-yfti-cnfc:64'>Calls lazily
+ -Action1<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border-top:solid #4F81BD 1.0pt;
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
@@ -13337,8 +13316,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'>
@@ -13364,8 +13342,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>
@@ -13487,15 +13465,14 @@
 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;
 mso-border-bottom-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 [Source_<0>() ==
- Event_<1>()]<o:p></o:p>
+ "Times New Roman";mso-ansi-language:EN'>[Source_<0>() == Event_<1>()]<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'>
@@ -13534,9 +13511,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 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;
@@ -13605,9 +13581,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
- 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'>
 
 <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'>
 ++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'>
@@ -14323,12 +14298,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
@@ -14393,8 +14368,8 @@
lang=EN style='mso-ansi-language:EN'><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'>
 <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;
@@ -16282,8 +16257,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'>
@@ -16535,8 +16510,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'>
@@ -16606,8 +16581,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'>
@@ -16990,8 +16965,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;
@@ -17012,8 +16987,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'>
@@ -17047,8 +17022,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'>
@@ -17080,8 +17055,7 @@
 EN'>const charT* data()<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border:none;padding:0cm 5.4pt 0cm 5.4pt'>
- const charT*
- string_data_(container)<o:p></o:p>
+ const charT* string_data_(container)<o:p></o:p>
 </td>
 <td width=248 valign=top style='width:148.85pt;border:none;border-right:solid #4F81BD 1.0pt;
 mso-border-right-themecolor:accent1;padding:0cm 5.4pt 0cm 5.4pt'>
@@ -17092,8 +17066,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;
@@ -17153,8 +17127,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'>
@@ -17188,8 +17162,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'>
@@ -17296,8 +17270,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>
@@ -17310,7 +17284,8 @@
 <td width=437 valign=top style='width:261.95pt;border:solid #4F81BD 1.0pt;
 mso-border-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 size_type find_first_of (charT c, size_type pos=0)<o:p></o:p>
+ style='mso-ansi-language:EN'>size_type find_first_of (charT c, size_type
+ pos=0)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border-top:solid #4F81BD 1.0pt;
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
@@ -17369,8 +17344,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>
@@ -17407,8 +17382,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'>
@@ -17493,8 +17468,7 @@
 <td width=437 valign=top style='width:261.95pt;border:solid #4F81BD 1.0pt;
 mso-border-themecolor:accent1;border-right:none;padding:0cm 5.4pt 0cm 5.4pt'>
 size_type find_last_not_of (charT* s, size_type
- pos=npos)<o:p></o:p>
+ style='mso-ansi-language:EN'>size_type find_last_not_of (charT* s, size_type pos=npos)<o:p></o:p>
 </td>
 <td width=437 valign=top style='width:262.25pt;border-top:solid #4F81BD 1.0pt;
 mso-border-top-themecolor:accent1;border-left:none;border-bottom:solid #4F81BD 1.0pt;
@@ -17519,8 +17493,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'>
@@ -17588,13 +17562,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
@@ -17716,13 +17690,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;
@@ -17807,8 +17781,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>
@@ -17906,13 +17880,14 @@

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

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

VC9:<o:p></o:p>
@@ -17939,8 +17914,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>
@@ -17985,10 +17960,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>
@@ -18141,11 +18116,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>

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>

#define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS<o:p></o:p></pre><pre>#define BOOST_MPL_LIMIT_VECTOR_SIZE 30 // or whatever you need<o:p></o:p></pre><pre>#define BOOST_MPL_LIMIT_MAP_SIZE 30 // or whatever you need<o:p></o:p></pre><pre><o:p> </o:p></pre>
+
+Question: Why do I get this error: ”error C2977: 'boost::mpl::vector' :
+too many template arguments”?<o:p></o:p>
+
+<pre>Answer: <o:p></o:p></pre><pre>The first possibility is that you defined a transition table as, say, vector17 and have 18 entries.<o:p></o:p></pre><pre>The second is that you have 17 entries and have a composite state. Under the hood, Msm adds a row for every event in the composite transition table.<o:p></o:p></pre><pre>The third one is that you used a mpl::vector without the number of entries but are close to the MPL default of 50 and have a composite, thus pushing you above 50. Then you need mpl/vector60/70….hpp and a mpl/map60/70….hpp<o:p></o:p></pre><pre><o:p> </o:p></pre></div>

</div>
@@ -18523,14 +18517,13 @@
disadvantages. <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
@@ -18612,7 +18605,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/image035.jpg" alt=clock.jpg v:shapes="Grafik_x0020_5"><![endif]><![endif]> 
<o:p></o:p>
@@ -18622,8 +18615,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/image036.jpg" alt=alarm.jpg v:shapes="Grafik_x0020_6"><![endif]><![endif]> 
<o:p></o:p>
@@ -18677,10 +18670,11 @@
lang=EN-US style='font-family:"Courier New";mso-ansi-language:EN-US'><o:p> </o:p>

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

<o:p> </o:p>
@@ -18807,8 +18801,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/image037.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/image038.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>

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

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

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

                                
-NoAction(), <o:p></o:p>
+style='mso-spacerun:yes'>                         
+       NoAction(), <o:p></o:p>

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

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

@@ -19503,10 +19499,8 @@
mso-layout-grid-align:none;text-autospace:none'>         
-      ) ) ) transition_table;<o:p></o:p>
+style='mso-spacerun:yes'>               
+) ) ) transition_table;<o:p></o:p>

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

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

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

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

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

Normally, one does not need to know the
-ids generated for all the states of a state machine, unless for debugging
+lang=EN-US style='mso-ansi-language:EN-US'>Normally, one does not need to know
+the ids generated for all the states of a state machine, unless for debugging
purposes, like the pstate function does in the tutorials in order to display the name of the
@@ -19628,7 +19623,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/image039.jpg" alt=AnnexA.jpg v:shapes="Grafik_x0020_9"><![endif]><![endif]> 
<o:p></o:p>
@@ -19695,11 +19690,11 @@

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

To achieve this, Msm provides a few

Next message: hartmut.kaiser_at_[hidden]: "[Boost-commit] svn:boost r57984 - trunk/libs/program_options/src"
Previous message: ramey_at_[hidden]: "[Boost-commit] svn:boost r57982 - in trunk/libs/serialization: doc src util vc7ide"

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