From e5205c86765bc6fa2b7c1aed66d7fa0118437d7e Mon Sep 17 00:00:00 2001
From: Mark Olesen <Mark.Olesen@Germany>
Date: Wed, 7 Jan 2009 10:52:31 +0100
Subject: [PATCH] minor docu change

---
 src/OpenFOAM/memory/Xfer/Xfer.H | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/src/OpenFOAM/memory/Xfer/Xfer.H b/src/OpenFOAM/memory/Xfer/Xfer.H
index 19a67c7af3..5d956a6e7f 100644
--- a/src/OpenFOAM/memory/Xfer/Xfer.H
+++ b/src/OpenFOAM/memory/Xfer/Xfer.H
@@ -41,7 +41,7 @@ Description
     xferMoveTo() functions can prove useful. An example is transferring
     from a DynamicList to a List.  Since the
     List\<T\>::transfer(List\<T\>&) method could result in some allocated
-    memory becoming inaccessible, the xferMoveTo() function can be used to
+    memory becoming inaccessible, the xferMoveTo() function should be used to
     invoke the correct List\<T\>::transfer(DynamicList\<T\>&) method.
 
     @code
@@ -50,6 +50,16 @@ Description
         labelList plainLst( xferMoveTo<labelList>(dynLst) );
     @endcode
 
+    Of course, since this example is a very common operation, the
+    DynamicList::xfer() method transfers to a plain List anyhow.
+    It would thus be simpler (and clearer) just to use the following code:
+
+    @code
+        DynamicList<label> dynLst;
+        ...
+        labelList plainLst(dynLst.xfer());
+    @endcode
+
 SeeAlso
     xferCopy, xferCopyTo, xferMove, xferMoveTo, xferTmp