Ticket #7458: serialization.patch

libs/serialization/doc/extended_type_info.html

@@ -309 +309 @@
 </dd>
 
 <dt><h4><code style="white-space: normal"><pre>
-virtual void * destroy(void const * const ptr ) ) const;
+virtual void * destroy(void const * const ptr ) const;
 </pre></code></h4></dt>
 <dd>
 Destroy an instance of this type. This calls the

libs/serialization/doc/implementation.html

@@ -225 +225 @@
 <ul>
     <li>The serialization library depends on the templated stream 
     implementation to function properly.
-    to function properly.  So STLPort must be used to build the library.
+    So STLPort must be used to build the library.
     <li>Polymorphic archive tests fail.
     <li>XML serialization only works with version 1.6x of spirit. In order to build 
     and use this library with this compiler, one must use version 1.6x rather than the 

libs/serialization/doc/singleton.html

@@ -137 +137 @@
 In order to be used as 
 <a target="singleton.hpp" href = "../../../boost/serialization/singleton.hpp">
 <code style="white-space: normal">
-singleton&lt;T&gt;
-</code> 
-</a>
-, the type T must be default constructable.
+singleton&lt;T&gt;</code></a>, the type T must be default constructable.
 It doesn't require static variables - though it may have them.
 Since the library guarentees that only one instance of 
 <a target="singleton.hpp" href = "../../../boost/serialization/singleton.hpp">
 <code style="white-space: normal">
-singleton&lt;T&gt;
-</code> 
-</a>
+singleton&lt;T&gt;</code></a>
 and all accesss is through the above static interface
 functions, common member functions of T become
 the functional equivalent of 
@@ -162 +157 @@
 which contains the following code:
 
 <pre><code>
-typedef std::set<const extended_type_info *, key_compare> ktmap;
+typedef std::set&lt;const extended_type_info *, key_compare&gt; ktmap;
 ...
 void
 extended_type_info::key_register(const char *key) {
     ...
-    result = singleton<ktmap>::get_mutable_instance().insert(this);
+    result = singleton&lt;ktmap&gt;::get_mutable_instance().insert(this);
     ...
 }
 </code></pre>
@@ -180 +175 @@
 A second way is to use 
 <a target="singleton.hpp" href = "../../../boost/serialization/singleton.hpp">
 <code style="white-space: normal">
-singleton&lt;T&gt;
-</code> 
-</a>
+singleton&lt;T&gt;</code></a>
 as one of the base classes of the type.  This is illustrated by a simplified
 excerpt from
 <a target="extended_type_info_typeid.hpp" href = "../../../boost/serialization/extended_type_info_typeid.hpp">

libs/serialization/doc/tutorial.html

@@ -327 +327 @@
 classes to be serialized. This is referred to as "registration" or "export"
 of derived classes.  This requirement and the methods of
 satisfying it are explained in detail
-<a href="serialization.html#derivedpointers">here</a>
+<a href="serialization.html#derivedpointers">here</a>.
 <p>
 All this is accomplished automatically by the serialization
 library.  The above code is all that is necessary to accomplish