Cosmetic formatting and doc updates in std_unique_ptr.i files

Lib/csharp/std_unique_ptr.i

@@ -1,10 +1,11 @@
 /* -----------------------------------------------------------------------------
  * std_unique_ptr.i
  *
- * The typemaps here allow handling functions returning std::unique_ptr<>,
+ * SWIG library file for handling std::unique_ptr.
- * which is the most common use of this type. If you have functions taking it
+ * Memory ownership is passed from the std::unique_ptr C++ layer to the proxy
- * as parameter, these typemaps can't be used for them and you need to do
+ * class when returning a std::unique_ptr from a function.
- * something else (e.g. use shared_ptr<> which SWIG supports fully).
+ * Memory ownership is passed from the proxy class to the std::unique_ptr in the
+ * C++ layer when passed as a parameter to a wrapped function.
  * ----------------------------------------------------------------------------- */
 
 %define %unique_ptr(TYPE)
@@ -20,11 +21,13 @@
 %typemap (out) std::unique_ptr< TYPE > %{
   $result = (void *)$1.release();
 %}
+
 %typemap(csout, excode=SWIGEXCODE) std::unique_ptr< TYPE > {
     System.IntPtr cPtr = $imcall;
     $typemap(cstype, TYPE) ret = (cPtr == System.IntPtr.Zero) ? null : new $typemap(cstype, TYPE)(cPtr, true);$excode
     return ret;
   }
+
 %template() std::unique_ptr< TYPE >;
 %enddef
 

Lib/java/std_unique_ptr.i

@@ -1,10 +1,11 @@
 /* -----------------------------------------------------------------------------
  * std_unique_ptr.i
  *
- * The typemaps here allow handling functions returning std::unique_ptr<>,
+ * SWIG library file for handling std::unique_ptr.
- * which is the most common use of this type. If you have functions taking it
+ * Memory ownership is passed from the std::unique_ptr C++ layer to the proxy
- * as parameter, these typemaps can't be used for them and you need to do
+ * class when returning a std::unique_ptr from a function.
- * something else (e.g. use shared_ptr<> which SWIG supports fully).
+ * Memory ownership is passed from the proxy class to the std::unique_ptr in the
+ * C++ layer when passed as a parameter to a wrapped function.
  * ----------------------------------------------------------------------------- */
 
 %define %unique_ptr(TYPE)

Lib/perl5/std_unique_ptr.i

@@ -1,10 +1,11 @@
 /* -----------------------------------------------------------------------------
  * std_unique_ptr.i
  *
- * The typemaps here allow handling functions returning std::unique_ptr<>,
+ * SWIG library file for handling std::unique_ptr.
- * which is the most common use of this type. If you have functions taking it
+ * Memory ownership is passed from the std::unique_ptr C++ layer to the proxy
- * as parameter, these typemaps can't be used for them and you need to do
+ * class when returning a std::unique_ptr from a function.
- * something else (e.g. use shared_ptr<> which SWIG supports fully).
+ * Memory ownership is passed from the proxy class to the std::unique_ptr in the
+ * C++ layer when passed as a parameter to a wrapped function.
  * ----------------------------------------------------------------------------- */
 
 %define %unique_ptr(TYPE)

Lib/python/std_unique_ptr.i

@@ -1,10 +1,11 @@
 /* -----------------------------------------------------------------------------
  * std_unique_ptr.i
  *
- * The typemaps here allow handling functions returning std::unique_ptr<>,
+ * SWIG library file for handling std::unique_ptr.
- * which is the most common use of this type. If you have functions taking it
+ * Memory ownership is passed from the std::unique_ptr C++ layer to the proxy
- * as parameter, these typemaps can't be used for them and you need to do
+ * class when returning a std::unique_ptr from a function.
- * something else (e.g. use shared_ptr<> which SWIG supports fully).
+ * Memory ownership is passed from the proxy class to the std::unique_ptr in the
+ * C++ layer when passed as a parameter to a wrapped function.
  * ----------------------------------------------------------------------------- */
 
 %define %unique_ptr(TYPE)

Lib/ruby/std_unique_ptr.i

@@ -1,10 +1,11 @@
 /* -----------------------------------------------------------------------------
  * std_unique_ptr.i
  *
- * The typemaps here allow handling functions returning std::unique_ptr<>,
+ * SWIG library file for handling std::unique_ptr.
- * which is the most common use of this type. If you have functions taking it
+ * Memory ownership is passed from the std::unique_ptr C++ layer to the proxy
- * as parameter, these typemaps can't be used for them and you need to do
+ * class when returning a std::unique_ptr from a function.
- * something else (e.g. use shared_ptr<> which SWIG supports fully).
+ * Memory ownership is passed from the proxy class to the std::unique_ptr in the
+ * C++ layer when passed as a parameter to a wrapped function.
  * ----------------------------------------------------------------------------- */
 
 %define %unique_ptr(TYPE)