[Boost-commit] svn:boost r56275 - trunk/libs/serialization/doc

Subject: [Boost-commit] svn:boost r56275 - trunk/libs/serialization/doc
From: ramey_at_[hidden]
Date: 2009-09-17 11:37:43

Author: ramey
Date: 2009-09-17 11:37:42 EDT (Thu, 17 Sep 2009)
New Revision: 56275
URL: http://svn.boost.org/trac/boost/changeset/56275

Log:
fixed extra ' in files
Text files modified: 
   trunk/libs/serialization/doc/serialization.html |    18 +++++++++---------                      
   trunk/libs/serialization/doc/special.html       |     8 ++++----                                
   trunk/libs/serialization/doc/traits.html        |     6 +++---                                  
   3 files changed, 16 insertions(+), 16 deletions(-)

Modified: trunk/libs/serialization/doc/serialization.html
==============================================================================
--- trunk/libs/serialization/doc/serialization.html	(original)
+++ trunk/libs/serialization/doc/serialization.html	2009-09-17 11:37:42 EDT (Thu, 17 Sep 2009)
@@ -175,7 +175,7 @@
 
 Note that we have called this override "non-intrusive".  This is slightly
 inaccurate.  It does not require that the class have special functions, that
-it be de'ived from some common base class or any other fundamental design changes.
+it be derived from some common base class or any other fundamental design changes.
 However, it will require access to the class members that are to
 be saved and loaded.  If these members are <code style="white-space: normal">private</code>, it won't be
 possible to serialize them.  So in some instances, minor modifications to the
@@ -256,7 +256,7 @@
 <pre><code>
     ar &amp; const_cast&lt;T &amp;&gt;(t);
 </code></pre>
-Note that this violates the spirit and inten'ion of the <code style="white-space: normal">const</code>
+Note that this violates the spirit and intention of the <code style="white-space: normal">const</code>
 keyword. <code style="white-space: normal">const</code> members are intialized when a class instance
 is constructed and not changed thereafter.  However, this may
 be most appropriate in many cases.  Ultimately, it comes down to 
@@ -334,7 +334,7 @@
 </code></pre>
 
 <h3><a name="splitting">Splitting <code style="white-space: normal">serialize</code> into Save/Load</a></h3>
-There are times when it is inconvenient to use the'same
+There are times when it is inconvenient to use the same
 template for both save and load functions.  For example, this might occur if versioning
 gets complex.  
 
@@ -437,7 +437,7 @@
 operator and <code style="white-space: normal">serialize</code>
 function guarantees that this is always the case and will minimize the
 occurence of hard to find errors related to synchronization of 
-<code styl'="white-space: normal">save</code> and <code style="white-space: normal">load</code> 
+<code style="white-space: normal">save</code> and <code style="white-space: normal">load</code> 
 functions.
 <p>
 Also note that <code style="white-space: normal">BOOST_SERIALIZATION_SPLIT_FREE</code>
@@ -527,7 +527,7 @@
     ::new(t)T();
 }
 </code></pre>
-The default 'code style="white-space: normal">load_construct_data</code> invokes the
+The default <code style="white-space: normal">load_construct_data</code> invokes the
 default constructor "in-place" to initialize the memory.
 <p>
 If there is no such default constructor, the function templates
@@ -627,7 +627,7 @@
 the class being read.  Note that this implies that "registration" has to occur
 during both save and load so that the class-integer table built on load
 is identical to the class-integer table built on save. In fact, the key to
-whole serialization'system is that things are always saved and loaded in
+whole serialization system is that things are always saved and loaded in
 the same sequence.  This includes "registration".
 <p>
 Expanding our previous example:
@@ -724,7 +724,7 @@
 explictly by the program so normally code to serialize such classes
 would never be instantiated.  So in addition to including export key
 strings in an archive, <code style="white-space: normal">BOOST_CLASS_EXPORT_GUID</code> explicitly
-instant'ates the class serialization code for all archive classes used 
+instantiates the class serialization code for all archive classes used 
 by the program.  
 
 <h4><a name="selectivetracking">Selective Tracking</a></h4>
@@ -794,7 +794,7 @@
         boost::serialization::base_object&lt;base&gt;(*this);
         // method 2 : explicitly register base/derived relationship
         boost::serialization::void_cast_register&lt;derived, base&gt;(
-            static_cast&lt;derived *&gt;'NULL),
+            static_cast&lt;derived *&gt;=NULL),
             static_cast&lt;base *&gt;(NULL)
         )
     }
@@ -917,7 +917,7 @@
 <ul>
   <li>optional
   <li>variant
-  <l'>scoped_ptr
+  <li>scoped_ptr
   <li>shared_ptr
   <li>auto_ptr (demo)
 </ul>

Modified: trunk/libs/serialization/doc/special.html
==============================================================================
--- trunk/libs/serialization/doc/special.html	(original)
+++ trunk/libs/serialization/doc/special.html	2009-09-17 11:37:42 EDT (Thu, 17 Sep 2009)
@@ -177,7 +177,7 @@
 archives.  Including the class information in the archive assures us
 that they will be readable in the future even if the class definition
 is revised.  A light weight structure such as display pixel might be
-declared in a header l'ke this:
+declared in a header like this:
 
 <pre><code>
 #include &lt;boost/serialization/serialization.hpp&gt;
@@ -265,7 +265,7 @@
 information for instantiations of this template is never serialized.  This 
 process is described <a target="detail" href="traits.html#templates">above</a> and
 has been used for <a target="detail" href="wrappers.html#nvp"><strong>Name-Value Pairs</strong></a>.
-Wrappers would typically be assigned'such traits.
+Wrappers would typically be assigned such traits.
 <p>
 Another way to avoid this problem is to assign serialization traits
 to all specializations of the template <code style="white-space: normal">my_wrapper</code>
@@ -439,7 +439,7 @@
 from the main program but the code is loaded at runtime.  In this
 example, this code is loaded automatically when the program which
 uses it starts up, but it could just as well be loaded and unloaded 
-with an OS depende't API call.
+with an OS dependent API call.
 <p>
 Also included are
 <a href = "../test/test_dll_exported.cpp" target="test_dll_exported">
@@ -542,7 +542,7 @@
 
 <hr>
 <p><i>&copy; Copyright Robert Ramey 2002-2004. 
-Dist'ibuted under the Boost Software License, Version 1.0. (See
+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)
 </i></p>
 </body>

Modified: trunk/libs/serialization/doc/traits.html
==============================================================================
--- trunk/libs/serialization/doc/traits.html	(original)
+++ trunk/libs/serialization/doc/traits.html	2009-09-17 11:37:42 EDT (Thu, 17 Sep 2009)
@@ -178,7 +178,7 @@
 <ul>
   <li>For primitive, <code style="white-space: normal">track_never</code>.
   <li>For pointers, <code style="white-space: normal">track_never</code>.
-  That i', addresses of addresses are not tracked by default.
+  That is, addresses of addresses are not tracked by default.
   <li>All current serialization wrappers such as <code style="white-space: normal">boost::serialization::nvp</code>,
   <code style="white-space: normal">track_never</code>.
   <li>For all other types, <code style="white-space: normal">track_selectively</code>.
@@ -279,7 +279,7 @@
 will return the correct value for all compilers.
 
 <h3><a name="typeinfo">Type Information Implementation</a></h3>
-This last trait is also related to the serialization of ob'ects
+This last trait is also related to the serialization of objects
 through a base class pointer.  The implementation of this facility
 requires the ability to determine at run time the true type of the
 object that a base class pointer points to.  Different serialization
@@ -505,7 +505,7 @@
 <p>
 <table border>
 <tr><th align=left>parameter</th><th align=left>description</th><th align=left>permitted values</th><th align=left>default value</th></tr>
-<tr><td><code>T</code></td><td>target class<'td><td>class name<T></td><td>none</td></tr>            
+<tr><td><code>T</code></td><td>target class</td><td>class name<T></td><td>none</td></tr>            
 <tr><td><code>Level</code></td><td>implementation level</td><td><code>not_serializable<br>primitive_type<br>object_serializable<br>object_class_info</code></td><td>none</td></tr>  
 <tr><td><code>Tracking</code></td><td>tracking level</td><td><code>track_never<br>track_selectivly<br>track_always</code></td><td>none</td></tr>
 <tr><td><code>Version</code></td><td><code>class version</td><td>unsigned integer</td><td><code>0</code></td></tr>