[Boost-commit] svn:boost r53047 - trunk/libs/statechart/doc

Subject: [Boost-commit] svn:boost r53047 - trunk/libs/statechart/doc
From: daniel_james_at_[hidden]
Date: 2009-05-16 10:17:21

Author: danieljames
Date: 2009-05-16 10:17:20 EDT (Sat, 16 May 2009)
New Revision: 53047
URL: http://svn.boost.org/trac/boost/changeset/53047

Log:
Fix some validation errors.
Text files modified: 
   trunk/libs/statechart/doc/faq.html                |     2 +-                                      
   trunk/libs/statechart/doc/future_and_history.html |     4 ++--                                    
   trunk/libs/statechart/doc/reference.html          |    12 ++++++------                            
   3 files changed, 9 insertions(+), 9 deletions(-)

Modified: trunk/libs/statechart/doc/faq.html
==============================================================================
--- trunk/libs/statechart/doc/faq.html	(original)
+++ trunk/libs/statechart/doc/faq.html	2009-05-16 10:17:20 EDT (Sat, 16 May 2009)
@@ -345,7 +345,7 @@
   Machine().initiate();
   return 0;
 }</pre>
-  <p>The problem arises because <code>state_machine<>::~state_machine</code>
+  <p>The problem arises because <code>state_machine&lt;&gt;::~state_machine</code>
   inevitably destructs all remaining active states. At this time,
   <code>Machine::~Machine</code> has already been run, making it illegal to
   access any of the <code>Machine</code> members. This problem can be avoided

Modified: trunk/libs/statechart/doc/future_and_history.html
==============================================================================
--- trunk/libs/statechart/doc/future_and_history.html	(original)
+++ trunk/libs/statechart/doc/future_and_history.html	2009-05-16 10:17:20 EDT (Sat, 16 May 2009)
@@ -143,7 +143,7 @@
   <p>1.39.0</p>
   <ul>
     <li>Fixed a bug that prevented the use of boost::ref() with
-    fifo_scheduler&lt;&gt::create_processor&lt;&gt, reported by Steve
+    fifo_scheduler&lt;&gt;::create_processor&lt;&gt;, reported by Steve
     Hawkes</li>
   </ul>
 
@@ -163,7 +163,7 @@
       do I get an assert when I access the state machine from a state
       destructor?</a> (due to feedback from Jiang Miao)</li>
     <li>Added defaults for the last two template parameters of <a href=
-      "reference.html#ClassTemplatein_state_reaction">in_state_reaction<></a>
+      "reference.html#ClassTemplatein_state_reaction">in_state_reaction&lt;&gt;</a>
       (due to feedback from Sean Kelly)</li>
     <li>Adapted fifo_scheduler&lt;&gt; to the changed allocator interface of
       boost::function</li>

Modified: trunk/libs/statechart/doc/reference.html
==============================================================================
--- trunk/libs/statechart/doc/reference.html	(original)
+++ trunk/libs/statechart/doc/reference.html	2009-05-16 10:17:20 EDT (Sat, 16 May 2009)
@@ -2525,7 +2525,7 @@
   <p><b>Requires</b>: If called from a constructor of a direct or indirect
   subtype then the most-derived type must directly or indirectly derive from
   the <code>state</code> class template. If called from a destructor of a
-  direct or indirect subtype then the <code>state_machine<></code> subclass
+  direct or indirect subtype then the <code>state_machine&lt;&gt;</code> subclass
   portion must still exist<br>
   <b>Returns</b>: A reference to the outermost context, which is always the
   state machine this state belongs to<br></p>
@@ -2537,7 +2537,7 @@
   <p><b>Requires</b>: If called from a constructor of a direct or indirect
   subtype then the most-derived type must directly or indirectly derive from
   the <code>state</code> class template. If called from a destructor of a
-  direct or indirect subtype then the <code>state_machine<></code> subclass
+  direct or indirect subtype then the <code>state_machine&lt;&gt;</code> subclass
   portion must still exist<br>
   <b>Returns</b>: A reference to the const outermost context, which is always
   the state machine this state belongs to</p>
@@ -2549,8 +2549,8 @@
   <p><b>Requires</b>: If called from a constructor of a direct or indirect
   subtype then the most-derived type must directly or indirectly derive from
   the <code>state</code> class template. If called from a destructor of a
-  direct or indirect subtype with a <code>state_machine<></code> subtype as
-  argument then the <code>state_machine<></code> subclass portion must still
+  direct or indirect subtype with a <code>state_machine&lt;&gt;</code> subtype as
+  argument then the <code>state_machine&lt;&gt;</code> subclass portion must still
   exist<br>
   <b>Returns</b>: A reference to a direct or indirect context</p>
   <pre>
@@ -2562,8 +2562,8 @@
   <p><b>Requires</b>: If called from a constructor of a direct or indirect
   subtype then the most-derived type must directly or indirectly derive from
   the <code>state</code> class template. If called from a destructor of a
-  direct or indirect subtype with a <code>state_machine<></code> subtype as
-  argument then the <code>state_machine<></code> subclass portion must still
+  direct or indirect subtype with a <code>state_machine&lt;&gt;</code> subtype as
+  argument then the <code>state_machine&lt;&gt;</code> subclass portion must still
   exist<br>
   <b>Returns</b>: A reference to a const direct or indirect context</p>
   <pre>