Boost logo

Boost-Commit :

Subject: [Boost-commit] svn:boost r54589 - in sandbox/cloneable/libs/cloneable/doc: . html html/cloneable html/cloneable/tutorial
From: christian.schladetsch_at_[hidden]
Date: 2009-07-02 06:18:27


Author: cschladetsch
Date: 2009-07-02 06:18:26 EDT (Thu, 02 Jul 2009)
New Revision: 54589
URL: http://svn.boost.org/trac/boost/changeset/54589

Log:
updated

Text files modified:
   sandbox/cloneable/libs/cloneable/doc/cloneable.qbk | 22 ++++++++++++----------
   sandbox/cloneable/libs/cloneable/doc/html/cloneable/change_log.html | 2 +-
   sandbox/cloneable/libs/cloneable/doc/html/cloneable/intro.html | 2 +-
   sandbox/cloneable/libs/cloneable/doc/html/cloneable/tutorial/using_custom_allocators.html | 16 +++++++++-------
   sandbox/cloneable/libs/cloneable/doc/html/cloneable/tutorial/using_external_types.html | 4 ++--
   sandbox/cloneable/libs/cloneable/doc/html/index.html | 4 ++--
   6 files changed, 27 insertions(+), 23 deletions(-)

Modified: sandbox/cloneable/libs/cloneable/doc/cloneable.qbk
==============================================================================
--- sandbox/cloneable/libs/cloneable/doc/cloneable.qbk (original)
+++ sandbox/cloneable/libs/cloneable/doc/cloneable.qbk 2009-07-02 06:18:26 EDT (Thu, 02 Jul 2009)
@@ -49,7 +49,7 @@
 each type in a given class hierarchy. The user can supply their own base classes,
 or sensible defaults are generated.
 
-[1] Cloneable objects can be used in containers-of-pointers (based on a modified <emphasis>Boost.PtrContainer</emphasis> implementation), producing a 'heterogenous' container system with value semantics for comparison and copying, and emplace semantics for insertion. These containers are currently a part of the proposal as well, however it is intended that they eventually form a distinct library. This proposal will focus mostly on the single-object aspect of the system.
+[1] Cloneable objects can be used in containers-of-pointers (based on a modified [*Boost.PtrContainer] implementation), producing a 'heterogenous' container system with value semantics for comparison and copying, and emplace semantics for insertion. These containers are currently a part of the proposal as well, however it is intended that they eventually form a distinct library. This proposal will focus mostly on the single-object aspect of the system.
 
 [endsect]
 
@@ -254,8 +254,8 @@
 };
 ``
 
-There are of courswe many ways to do this, and how you do it will depend on many factors.
-Just bare in mind that `cloneable::adaptor<>` is there if you need it.
+There are of course many ways to do this, and how you do it will depend on many factors.
+Just bear in mind that `cloneable::adaptor<>` is there if you need it.
 
 Next, we look at how to customise the cloning operation itself, and how we can
 use our own or other allocators. This is important to understand before we
@@ -299,10 +299,12 @@
 
 [section Using Custom Allocators]
 
-The entire ['Cloneable] system was designed to support general allocators. This provides
-more fine-tuned control for the cloning and creation operations, and ensures Cloneable
-types work well in containers. When making a new object or sub-object or clone or sub-clone,
-the underlying `abstract_base` is given a reference to an `abstract_allocator`. This is
+The entire Cloneable system was designed to support general allocators. This provides
+more fine-tuned control over cloning and creation operations, and ensures Cloneable
+types work well in containers.
+
+When making a new object, sub-object, clone or sub-clone, the underlying `abstract_base`
+is given a reference to an `abstract_allocator`. This is
 an interface (containing only pure virtual methods) that is used to expose a specialised
 `allocator<T>` to the non-specific `abstract_base`. This process is easy to understand with some examples:
 
@@ -339,11 +341,11 @@
 ``
 
 Recall that if your class can be correctly copy-constructed, you do not need to
-provide a custom clone override at all. If your class members that have value
-semantics and can be copy-constructed (including `std::containers`, and heterogenous::containers),
+provide a custom clone override at all. If your class only members that have value
+semantics and can in turn be copy-constructed (including `std::containers`, and heterogenous::containers),
 then you do not need to provide any customisation.
 
-However, if your class containers pointers of any description, or references,
+However, if your class contains pointers of any description, or references,
 then you will in general have to provide a sensible copy-constructor, or provide a custom clone override.
 
 In summary, there are three stages of customisation:

Modified: sandbox/cloneable/libs/cloneable/doc/html/cloneable/change_log.html
==============================================================================
--- sandbox/cloneable/libs/cloneable/doc/html/cloneable/change_log.html (original)
+++ sandbox/cloneable/libs/cloneable/doc/html/cloneable/change_log.html 2009-07-02 06:18:26 EDT (Thu, 02 Jul 2009)
@@ -27,7 +27,7 @@
 <a name="cloneable.change_log"></a><a class="link" href="change_log.html" title="Change Log"> Change Log</a>
 </h2></div></div></div>
 <a name="cloneable.change_log.version_0_1"></a><h4>
-<a name="id671355"></a>
+<a name="id644054"></a>
       <a class="link" href="change_log.html#cloneable.change_log.version_0_1">Version 0.1</a>
     </h4>
 <div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">

Modified: sandbox/cloneable/libs/cloneable/doc/html/cloneable/intro.html
==============================================================================
--- sandbox/cloneable/libs/cloneable/doc/html/cloneable/intro.html (original)
+++ sandbox/cloneable/libs/cloneable/doc/html/cloneable/intro.html 2009-07-02 06:18:26 EDT (Thu, 02 Jul 2009)
@@ -54,7 +54,7 @@
     </p>
 <p>
       [1] Cloneable objects can be used in containers-of-pointers (based on a modified
- &lt;emphasis&gt;Boost.PtrContainer&lt;/emphasis&gt; implementation), producing
+ <span class="bold"><strong>Boost.PtrContainer</strong></span> implementation), producing
       a 'heterogenous' container system with value semantics for comparison and copying,
       and emplace semantics for insertion. These containers are currently a part
       of the proposal as well, however it is intended that they eventually form a

Modified: sandbox/cloneable/libs/cloneable/doc/html/cloneable/tutorial/using_custom_allocators.html
==============================================================================
--- sandbox/cloneable/libs/cloneable/doc/html/cloneable/tutorial/using_custom_allocators.html (original)
+++ sandbox/cloneable/libs/cloneable/doc/html/cloneable/tutorial/using_custom_allocators.html 2009-07-02 06:18:26 EDT (Thu, 02 Jul 2009)
@@ -27,10 +27,12 @@
       Allocators</a>
 </h3></div></div></div>
 <p>
- The entire <span class="emphasis"><em>Cloneable</em></span> system was designed to support
- general allocators. This provides more fine-tuned control for the cloning
- and creation operations, and ensures Cloneable types work well in containers.
- When making a new object or sub-object or clone or sub-clone, the underlying
+ The entire Cloneable system was designed to support general allocators. This
+ provides more fine-tuned control over cloning and creation operations, and
+ ensures Cloneable types work well in containers.
+ </p>
+<p>
+ When making a new object, sub-object, clone or sub-clone, the underlying
         <code class="computeroutput"><span class="identifier">abstract_base</span></code> is given a
         reference to an <code class="computeroutput"><span class="identifier">abstract_allocator</span></code>.
         This is an interface (containing only pure virtual methods) that is used
@@ -81,12 +83,12 @@
       </p>
 <p>
         Recall that if your class can be correctly copy-constructed, you do not need
- to provide a custom clone override at all. If your class members that have
- value semantics and can be copy-constructed (including <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">containers</span></code>,
+ to provide a custom clone override at all. If your class only members that
+ have value semantics and can in turn be copy-constructed (including <code class="computeroutput"><span class="identifier">std</span><span class="special">::</span><span class="identifier">containers</span></code>,
         and heterogenous::containers), then you do not need to provide any customisation.
       </p>
 <p>
- However, if your class containers pointers of any description, or references,
+ However, if your class contains pointers of any description, or references,
         then you will in general have to provide a sensible copy-constructor, or
         provide a custom clone override.
       </p>

Modified: sandbox/cloneable/libs/cloneable/doc/html/cloneable/tutorial/using_external_types.html
==============================================================================
--- sandbox/cloneable/libs/cloneable/doc/html/cloneable/tutorial/using_external_types.html (original)
+++ sandbox/cloneable/libs/cloneable/doc/html/cloneable/tutorial/using_external_types.html 2009-07-02 06:18:26 EDT (Thu, 02 Jul 2009)
@@ -79,8 +79,8 @@
 <p>
       </p>
 <p>
- There are of courswe many ways to do this, and how you do it will depend
- on many factors. Just bare in mind that <code class="computeroutput"><span class="identifier">cloneable</span><span class="special">::</span><span class="identifier">adaptor</span><span class="special">&lt;&gt;</span></code> is there if you need it.
+ There are of course many ways to do this, and how you do it will depend on
+ many factors. Just bear in mind that <code class="computeroutput"><span class="identifier">cloneable</span><span class="special">::</span><span class="identifier">adaptor</span><span class="special">&lt;&gt;</span></code> is there if you need it.
       </p>
 <p>
         Next, we look at how to customise the cloning operation itself, and how we

Modified: sandbox/cloneable/libs/cloneable/doc/html/index.html
==============================================================================
--- sandbox/cloneable/libs/cloneable/doc/html/index.html (original)
+++ sandbox/cloneable/libs/cloneable/doc/html/index.html 2009-07-02 06:18:26 EDT (Thu, 02 Jul 2009)
@@ -28,7 +28,7 @@
 </h3></div></div></div>
 <div><p class="copyright">Copyright © 2009 Christian Schladetsch</p></div>
 <div><div class="legalnotice" title="Legal Notice">
-<a name="id671270"></a><p>
+<a name="id643964"></a><p>
         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)
       </p>
@@ -56,7 +56,7 @@
 </div>
 </div>
 <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
-<td align="left"><p><small>Last revised: July 02, 2009 at 09:22:22 GMT</small></p></td>
+<td align="left"><p><small>Last revised: July 02, 2009 at 10:17:51 GMT</small></p></td>
 <td align="right"><div class="copyright-footer"></div></td>
 </tr></table>
 <hr>


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