[Boost-commit] svn:boost r52128 - trunk/libs/exception/doc

Subject: [Boost-commit] svn:boost r52128 - trunk/libs/exception/doc
From: emil_at_[hidden]
Date: 2009-04-02 01:39:44

Author: emildotchevski
Date: 2009-04-02 01:39:42 EDT (Thu, 02 Apr 2009)
New Revision: 52128
URL: http://svn.boost.org/trac/boost/changeset/52128

Log:
documentation update
Text files modified: 
   trunk/libs/exception/doc/boost-exception.html                              |     2 +-                                      
   trunk/libs/exception/doc/exception.html                                    |     2 +-                                      
   trunk/libs/exception/doc/exception_types_as_simple_semantic_tags.html      |     2 +-                                      
   trunk/libs/exception/doc/motivation.html                                   |     2 +-                                      
   trunk/libs/exception/doc/name_idx.html                                     |     2 +-                                      
   trunk/libs/exception/doc/using_virtual_inheritance_in_exception_types.html |     2 +-                                      
   6 files changed, 6 insertions(+), 6 deletions(-)

Modified: trunk/libs/exception/doc/boost-exception.html
==============================================================================
--- trunk/libs/exception/doc/boost-exception.html	(original)
+++ trunk/libs/exception/doc/boost-exception.html	2009-04-02 01:39:42 EDT (Thu, 02 Apr 2009)
@@ -30,7 +30,7 @@
 <li><span class="RenoLink">Diagnostic Information</span></li>
 <li><span class="RenoLink">Integrating Boost Exception in Existing Exception Class Hierarchies</span></li>
 <li><span class="RenoLink">Transporting of Exceptions Between Threads</span></li>
-<li><span class="RenoLink">Exception Types As Simple Semantic Tags</span></li>
+<li><span class="RenoLink">Exception Types as Simple Semantic Tags</span></li>
 <li><span class="RenoLink">Using Virtual Inheritance in Exception Types</span></li>
 </ol></div>
 </li>

Modified: trunk/libs/exception/doc/exception.html
==============================================================================
--- trunk/libs/exception/doc/exception.html	(original)
+++ trunk/libs/exception/doc/exception.html	2009-04-02 01:39:42 EDT (Thu, 02 Apr 2009)
@@ -47,7 +47,7 @@
 </a><a href="current_exception.html">current_exception<br/>
 </a><a href="tutorial_diagnostic_information.html">Diagnostic Information<br/>
 </a><a href="diagnostic_information.html">diagnostic_information<br/>
-</a><a href="exception_types_as_simple_semantic_tags.html">Exception Types As Simple Semantic Tags<br/>
+</a><a href="exception_types_as_simple_semantic_tags.html">Exception Types as Simple Semantic Tags<br/>
 </a><a href="enable_current_exception.html">enable_current_exception<br/>
 </a><a href="enable_error_info.html">enable_error_info<br/>
 </a><a href="error_info.html">error_info<br/>

Modified: trunk/libs/exception/doc/exception_types_as_simple_semantic_tags.html
==============================================================================
--- trunk/libs/exception/doc/exception_types_as_simple_semantic_tags.html	(original)
+++ trunk/libs/exception/doc/exception_types_as_simple_semantic_tags.html	2009-04-02 01:39:42 EDT (Thu, 02 Apr 2009)
@@ -19,7 +19,7 @@
 <!-- Copyright (c) 2006-2009 Emil Dotchevski and Reverge Studios, Inc. -->
 <!-- Distributed under the Boost Software License, Version 1.0. (See accompanying -->
 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
-<div class="RenoIncludeDIV"><div class="RenoAutoDIV"><h3>Exception Types As Simple Semantic Tags</h3>
+<div class="RenoIncludeDIV"><div class="RenoAutoDIV"><h3>Exception Types as Simple Semantic Tags</h3>
 </div>
 <p>Deriving from boost::<span class="RenoLink">exception</span> effectively decouples the semantics of a failure from the information that is relevant to each individual instance of reporting a failure with a given semantic.</p>
 <p>In other words: with boost::<span class="RenoLink">exception</span>, what data a given exception object transports depends primarily on the context in which failures are reported (not on its type.) Since exception types need no members, it becomes very natural to throw exceptions that derive from more than one type to indicate multiple appropriate semantics:</p>

Modified: trunk/libs/exception/doc/motivation.html
==============================================================================
--- trunk/libs/exception/doc/motivation.html	(original)
+++ trunk/libs/exception/doc/motivation.html	2009-04-02 01:39:42 EDT (Thu, 02 Apr 2009)
@@ -123,7 +123,7 @@
 </div><div class="RenoAutoDIV"><div class="RenoHR"><hr/></div>
 <h3>See Also:</h3>
 <div class="RenoPageList"><a href="boost-exception.html">Boost Exception<br/>
-</a><a href="exception_types_as_simple_semantic_tags.html">Exception Types As Simple Semantic Tags<br/>
+</a><a href="exception_types_as_simple_semantic_tags.html">Exception Types as Simple Semantic Tags<br/>
 </a><a href="frequently_asked_questions.html">Frequently Asked Questions<br/>
 </a><a href="tutorial_enable_error_info.html">Integrating Boost Exception in Existing Exception Class Hierarchies<br/>
 </a></div>

Modified: trunk/libs/exception/doc/name_idx.html
==============================================================================
--- trunk/libs/exception/doc/name_idx.html	(original)
+++ trunk/libs/exception/doc/name_idx.html	2009-04-02 01:39:42 EDT (Thu, 02 Apr 2009)
@@ -45,7 +45,7 @@
 <h3>d</h3>
 <p>diagnostic_information</p>
 <h3>E</h3>
-<p>Exception Types As Simple Semantic Tags</p>
+<p>Exception Types as Simple Semantic Tags</p>
 <h3>e</h3>
 <p>enable_current_exception</p>
 <p>enable_error_info</p>

Modified: trunk/libs/exception/doc/using_virtual_inheritance_in_exception_types.html
==============================================================================
--- trunk/libs/exception/doc/using_virtual_inheritance_in_exception_types.html	(original)
+++ trunk/libs/exception/doc/using_virtual_inheritance_in_exception_types.html	2009-04-02 01:39:42 EDT (Thu, 02 Apr 2009)
@@ -35,7 +35,7 @@
     catch(...) { std::cout &lt;&lt; "whoops!" &lt;&lt; std::endl; }
     }</pre>
 <p>The program above outputs "whoops!" because the conversion to std::exception is ambiguous.</p>
-<p>The overhead introduced by virtual inheritance is always negligible in the context of exception handling. Note that virtual bases are initialized directly by the constructor of the most-derived-type (the type passed to the throw statement, in case of exceptions.) However, typically this detail is of no concern when boost::<span class="RenoLink">exception</span> is used, because it enables exception types to be trivial structs with no members (there's nothing to initialize.) See <span class="RenoLink">Exception Types As Simple Semantic Tags</span>.</p>
+<p>The overhead introduced by virtual inheritance is always negligible in the context of exception handling. Note that virtual bases are initialized directly by the constructor of the most-derived-type (the type passed to the throw statement, in case of exceptions.) However, typically this detail is of no concern when boost::<span class="RenoLink">exception</span> is used, because it enables exception types to be trivial structs with no members (there's nothing to initialize.) See <span class="RenoLink">Exception Types as Simple Semantic Tags</span>.</p>
 </div><div class="RenoAutoDIV"><div class="RenoHR"><hr/></div>
 <h3>See Also:</h3>
 <div class="RenoPageList"><a href="boost-exception.html">Boost Exception<br/>