boost-react-native-bundle

<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=US-ASCII"> <title>Class communicator</title> <link rel="stylesheet" href="../../../../doc/src/boostbook.css" type="text/css"> <meta name="generator" content="DocBook XSL Stylesheets V1.78.1"> <link rel="home" href="../../index.html" title="The Boost C++ Libraries BoostBook Documentation Subset"> <link rel="up" href="../../mpi/reference.html#header.boost.mpi.communicator_hpp" title="Header <boost/mpi/communicator.hpp>"> <link rel="prev" href="scan.html" title="Function scan"> <link rel="next" href="comm_create_kind.html" title="Type comm_create_kind"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <table cellpadding="2" width="100%"><tr> <td valign="top"><img alt="Boost C++ Libraries" width="277" height="86" src="../../../../boost.png"></td> <td align="center"><a href="../../../../index.html">Home</a></td> <td align="center"><a href="../../../../libs/libraries.htm">Libraries</a></td> <td align="center"><a href="http://www.boost.org/users/people.html">People</a></td> <td align="center"><a href="http://www.boost.org/users/faq.html">FAQ</a></td> <td align="center"><a href="../../../../more/index.htm">More</a></td> </tr></table> <hr> <div class="spirit-nav"> <a accesskey="p" href="scan.html"><img src="../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../mpi/reference.html#header.boost.mpi.communicator_hpp"><img src="../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../index.html"><img src="../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="comm_create_kind.html"><img src="../../../../doc/src/images/next.png" alt="Next"></a> </div> <div class="refentry"> <a name="boost.mpi.communicator"></a><div class="titlepage"></div> <div class="refnamediv"> <h2>Class communicator</h2> boost::mpi::communicator — A communicator that permits communication and synchronization among a set of processes. </div> <h2 xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv-title">Synopsis</h2> <div xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" class="refsynopsisdiv"><pre class="synopsis">// In header: <<a class="link" href="../../mpi/reference.html#header.boost.mpi.communicator_hpp" title="Header <boost/mpi/communicator.hpp>">boost/mpi/communicator.hpp</a>> class <a class="link" href="communicator.html" title="Class communicator">communicator</a> { public: // <a class="link" href="communicator.html#boost.mpi.communicatorconstruct-copy-destruct">construct/copy/destruct</a> <a class="link" href="communicator.html#idp223510432-bb">communicator</a>(); <a class="link" href="communicator.html#idp154392800-bb">communicator</a>(const MPI_Comm &, comm_create_kind); <a class="link" href="communicator.html#idp222033376-bb">communicator</a>(const <a class="link" href="communicator.html" title="Class communicator">communicator</a> &, const <a class="link" href="group.html" title="Class group">boost::mpi::group</a> &); // <a class="link" href="communicator.html#idp152526672-bb">public member functions</a> int <a class="link" href="communicator.html#idp229851616-bb">rank</a>() const; int <a class="link" href="communicator.html#idp229854576-bb">size</a>() const; <a class="link" href="group.html" title="Class group">boost::mpi::group</a> <a class="link" href="communicator.html#idp229857456-bb">group</a>() const; template<typename T> void <a class="link" href="communicator.html#idp229859664-bb">send</a>(int, int, const T &) const; template<typename T> void <a class="link" href="communicator.html#idp161908512-bb">send</a>(int, int, const <a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a>< T > &) const; template<typename T> void <a class="link" href="communicator.html#idp144481888-bb">send</a>(int, int, const T *, int) const; void <a class="link" href="communicator.html#idp153555408-bb">send</a>(int, int) const; template<typename T> <a class="link" href="status.html" title="Class status">status</a> <a class="link" href="communicator.html#idp153560864-bb">recv</a>(int, int, T &) const; template<typename T> <a class="link" href="status.html" title="Class status">status</a> <a class="link" href="communicator.html#idp228664608-bb">recv</a>(int, int, const <a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a>< T > &) const; template<typename T> <a class="link" href="status.html" title="Class status">status</a> <a class="link" href="communicator.html#idp153663552-bb">recv</a>(int, int, <a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a>< T > &) const; template<typename T> <a class="link" href="status.html" title="Class status">status</a> <a class="link" href="communicator.html#idp155663504-bb">recv</a>(int, int, T *, int) const; <a class="link" href="status.html" title="Class status">status</a> <a class="link" href="communicator.html#idp149298752-bb">recv</a>(int, int) const; template<typename T> <a class="link" href="request.html" title="Class request">request</a> <a class="link" href="communicator.html#idp228678816-bb">isend</a>(int, int, const T &) const; template<typename T> <a class="link" href="request.html" title="Class request">request</a> <a class="link" href="communicator.html#idp102076112-bb">isend</a>(int, int, const <a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a>< T > &) const; template<typename T> <a class="link" href="request.html" title="Class request">request</a> <a class="link" href="communicator.html#idp218602880-bb">isend</a>(int, int, const T *, int) const; <a class="link" href="request.html" title="Class request">request</a> <a class="link" href="communicator.html#idp216800144-bb">isend</a>(int, int) const; template<typename T> <a class="link" href="request.html" title="Class request">request</a> <a class="link" href="communicator.html#idp212820160-bb">irecv</a>(int, int, T &) const; template<typename T> <a class="link" href="request.html" title="Class request">request</a> <a class="link" href="communicator.html#idp212807760-bb">irecv</a>(int, int, T *, int) const; <a class="link" href="request.html" title="Class request">request</a> <a class="link" href="communicator.html#idp94644592-bb">irecv</a>(int, int) const; <a class="link" href="status.html" title="Class status">status</a> <a class="link" href="communicator.html#idp94652400-bb">probe</a>(int = any_source, int = any_tag) const; optional< <a class="link" href="status.html" title="Class status">status</a> > <a class="link" href="communicator.html#idp158973520-bb">iprobe</a>(int = any_source, int = any_tag) const; void <a class="link" href="communicator.html#idp70002112-bb">barrier</a>() const; <a class="link" href="communicator.html#idp229918736-bb">operator bool</a>() const; <a class="link" href="communicator.html#idp229921616-bb">operator MPI_Comm</a>() const; <a class="link" href="communicator.html" title="Class communicator">communicator</a> <a class="link" href="communicator.html#idp229924240-bb">split</a>(int) const; <a class="link" href="communicator.html" title="Class communicator">communicator</a> <a class="link" href="communicator.html#idp94828048-bb">split</a>(int, int) const; optional< <a class="link" href="intercommunicator.html" title="Class intercommunicator">intercommunicator</a> > <a class="link" href="communicator.html#idp157150368-bb">as_intercommunicator</a>() const; optional< <a class="link" href="graph_communicator.html" title="Class graph_communicator">graph_communicator</a> > <a class="link" href="communicator.html#idp157154032-bb">as_graph_communicator</a>() const; bool <a class="link" href="communicator.html#idp223503888-bb">has_cartesian_topology</a>() const; void <a class="link" href="communicator.html#idp223505472-bb">abort</a>(int) const; };</pre></div> <div class="refsect1"> <a name="idp338392624"></a><h2>Description</h2> The <code class="computeroutput">communicator</code> class abstracts a set of communicating processes in MPI. All of the processes that belong to a certain communicator can determine the size of the communicator, their rank within the communicator, and communicate with any other processes in the communicator. <div class="refsect2"> <a name="idp338394288"></a><h3> <a name="boost.mpi.communicatorconstruct-copy-destruct"></a><code class="computeroutput">communicator</code> public construct/copy/destruct</h3> <div class="orderedlist"><ol class="orderedlist" type="1"> <li class="listitem"> <pre class="literallayout"><a name="idp223510432-bb"></a>communicator();</pre> Build a new Boost.MPI communicator for <code class="computeroutput">MPI_COMM_WORLD</code>. Constructs a Boost.MPI communicator that attaches to <code class="computeroutput">MPI_COMM_WORLD</code>. This is the equivalent of constructing with <code class="computeroutput"></code>(MPI_COMM_WORLD, comm_attach). </li> <li class="listitem"> <pre class="literallayout"><a name="idp154392800-bb"></a>communicator(const MPI_Comm & comm, comm_create_kind kind);</pre> Build a new Boost.MPI communicator based on the MPI communicator <code class="computeroutput">comm</code>. <code class="computeroutput">comm</code> may be any valid MPI communicator. If <code class="computeroutput">comm</code> is MPI_COMM_NULL, an empty communicator (that cannot be used for communication) is created and the <code class="computeroutput">kind</code> parameter is ignored. Otherwise, the <code class="computeroutput">kind</code> parameters determines how the Boost.MPI communicator will be related to <code class="computeroutput">comm:</code> <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem">If <code class="computeroutput">kind</code> is <code class="computeroutput">comm_duplicate</code>, duplicate <code class="computeroutput">comm</code> to create a new communicator. This new communicator will be freed when the Boost.MPI communicator (and all copies of it) is destroyed. This option is only permitted if <code class="computeroutput">comm</code> is a valid MPI intracommunicator or if the underlying MPI implementation supports MPI 2.0 (which supports duplication of intercommunicators).</li> <li class="listitem">If <code class="computeroutput">kind</code> is <code class="computeroutput">comm_take_ownership</code>, take ownership of <code class="computeroutput">comm</code>. It will be freed automatically when all of the Boost.MPI communicators go out of scope. This option must not be used when <code class="computeroutput">comm</code> is MPI_COMM_WORLD.</li> <li class="listitem">If <code class="computeroutput">kind</code> is <code class="computeroutput">comm_attach</code>, this Boost.MPI communicator will reference the existing MPI communicator <code class="computeroutput">comm</code> but will not free <code class="computeroutput">comm</code> when the Boost.MPI communicator goes out of scope. This option should only be used when the communicator is managed by the user or MPI library (e.g., MPI_COMM_WORLD). </li> </ul></div> </li> <li class="listitem"> <pre class="literallayout"><a name="idp222033376-bb"></a>communicator(const <a class="link" href="communicator.html" title="Class communicator">communicator</a> & comm, const <a class="link" href="group.html" title="Class group">boost::mpi::group</a> & subgroup);</pre> Build a new Boost.MPI communicator based on a subgroup of another MPI communicator. This routine will construct a new communicator containing all of the processes from communicator <code class="computeroutput">comm</code> that are listed within the group <code class="computeroutput">subgroup</code>. Equivalent to <code class="computeroutput">MPI_Comm_create</code>. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody><tr> <td>Parameters:</td> <td><div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td><code class="computeroutput">comm</code></td> <td>An MPI communicator.</td> </tr> <tr> <td><code class="computeroutput">subgroup</code></td> <td>A subgroup of the MPI communicator, <code class="computeroutput">comm</code>, for which we will construct a new communicator. </td> </tr> </tbody> </table></div></td> </tr></tbody> </table></div> </li> </ol></div> </div> <div class="refsect2"> <a name="idp338442432"></a><h3> <a name="idp152526672-bb"></a><code class="computeroutput">communicator</code> public member functions</h3> <div class="orderedlist"><ol class="orderedlist" type="1"> <li class="listitem"> <pre class="literallayout">int <a name="idp229851616-bb"></a>rank() const;</pre>Determine the rank of the executing process in a communicator. This routine is equivalent to <code class="computeroutput">MPI_Comm_rank</code>. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody><tr> <td>Returns:</td> <td>The rank of the process in the communicator, which will be a value in [0, size()) </td> </tr></tbody> </table></div> </li> <li class="listitem"> <pre class="literallayout">int <a name="idp229854576-bb"></a>size() const;</pre>Determine the number of processes in a communicator. This routine is equivalent to <code class="computeroutput">MPI_Comm_size</code>. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody><tr> <td>Returns:</td> <td>The number of processes in the communicator. </td> </tr></tbody> </table></div> </li> <li class="listitem"> <pre class="literallayout"><a class="link" href="group.html" title="Class group">boost::mpi::group</a> <a name="idp229857456-bb"></a>group() const;</pre> This routine constructs a new group whose members are the processes within this communicator. Equivalent to calling <code class="computeroutput">MPI_Comm_group</code>. </li> <li class="listitem"> <pre class="literallayout">template<typename T> void <a name="idp229859664-bb"></a>send(int dest, int tag, const T & value) const;</pre>Send data to another process. This routine executes a potentially blocking send with tag <code class="computeroutput">tag</code> to the process with rank <code class="computeroutput">dest</code>. It can be received by the destination process with a matching <code class="computeroutput">recv</code> call. The given <code class="computeroutput">value</code> must be suitable for transmission over MPI. There are several classes of types that meet these requirements: <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "> <li class="listitem">Types with mappings to MPI data types: If <code class="computeroutput">is_mpi_datatype<T></code> is convertible to <code class="computeroutput">mpl::true_</code>, then <code class="computeroutput">value</code> will be transmitted using the MPI data type <code class="computeroutput">get_mpi_datatype<T>()</code>. All primitive C++ data types that have MPI equivalents, e.g., <code class="computeroutput">int</code>, <code class="computeroutput">float</code>, <code class="computeroutput">char</code>, <code class="computeroutput">double</code>, etc., have built-in mappings to MPI data types. You may turn a Serializable type with fixed structure into an MPI data type by specializing <code class="computeroutput"><code class="computeroutput"><a class="link" href="is_mpi_datatype.html" title="Struct template is_mpi_datatype">is_mpi_datatype</a></code></code> for your type.</li> <li class="listitem">Serializable types: Any type that provides the <code class="computeroutput">serialize()</code> functionality required by the Boost.Serialization library can be transmitted and received.</li> <li class="listitem">Packed archives and skeletons: Data that has been packed into an <code class="computeroutput"><code class="computeroutput"><a class="link" href="packed_oarchive.html" title="Class packed_oarchive">mpi::packed_oarchive</a></code></code> or the skeletons of data that have been backed into an <code class="computeroutput"><code class="computeroutput"><a class="link" href="packed_skeleton_oarchive.html" title="Class packed_skeleton_oarchive">mpi::packed_skeleton_oarchive</a></code></code> can be transmitted, but will be received as <code class="computeroutput"><code class="computeroutput"><a class="link" href="packed_iarchive.html" title="Class packed_iarchive">mpi::packed_iarchive</a></code></code> and <code class="computeroutput"><code class="computeroutput"><a class="link" href="packed_skeleton_iarchive.html" title="Class packed_skeleton_iarchive">mpi::packed_skeleton_iarchive</a></code></code>, respectively, to allow the values (or skeletons) to be extracted by the destination process.</li> <li class="listitem">Content: Content associated with a previously-transmitted skeleton can be transmitted by <code class="computeroutput">send</code> and received by <code class="computeroutput">recv</code>. The receiving process may only receive content into the content of a value that has been constructed with the matching skeleton.</li> </ul></div> For types that have mappings to an MPI data type (including the concent of a type), an invocation of this routine will result in a single MPI_Send call. For variable-length data, e.g., serialized types and packed archives, two messages will be sent via MPI_Send: one containing the length of the data and the second containing the data itself. Note that the transmission mode for variable-length data is an implementation detail that is subject to change. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody><tr> <td>Parameters:</td> <td><div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td><code class="computeroutput">dest</code></td> <td>The rank of the remote process to which the data will be sent.</td> </tr> <tr> <td><code class="computeroutput">tag</code></td> <td>The tag that will be associated with this message. Tags may be any integer between zero and an implementation-defined upper limit. This limit is accessible via <code class="computeroutput">environment::max_tag()</code>.</td> </tr> <tr> <td><code class="computeroutput">value</code></td> <td>The value that will be transmitted to the receiver. The type <code class="computeroutput">T</code> of this value must meet the aforementioned criteria for transmission. </td> </tr> </tbody> </table></div></td> </tr></tbody> </table></div> </li> <li class="listitem"> <pre class="literallayout">template<typename T> void <a name="idp161908512-bb"></a>send(int dest, int tag, const <a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a>< T > & proxy) const;</pre>Send the skeleton of an object. This routine executes a potentially blocking send with tag <code class="computeroutput">tag</code> to the process with rank <code class="computeroutput">dest</code>. It can be received by the destination process with a matching <code class="computeroutput">recv</code> call. This variation on <code class="computeroutput">send</code> will be used when a send of a skeleton is explicitly requested via code such as: <pre class="programlisting">comm.send(dest, tag, skeleton(object)); </pre> The semantics of this routine are equivalent to that of sending a <code class="computeroutput"><code class="computeroutput"><a class="link" href="packed_skeleton_oarchive.html" title="Class packed_skeleton_oarchive">packed_skeleton_oarchive</a></code></code> storing the skeleton of the <code class="computeroutput">object</code>. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody><tr> <td>Parameters:</td> <td><div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td><code class="computeroutput">dest</code></td> <td>The rank of the remote process to which the skeleton will be sent.</td> </tr> <tr> <td><code class="computeroutput">proxy</code></td> <td>The <code class="computeroutput"><code class="computeroutput"><a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a></code></code> containing a reference to the object whose skeleton will be transmitted. </td> </tr> <tr> <td><code class="computeroutput">tag</code></td> <td>The tag that will be associated with this message. Tags may be any integer between zero and an implementation-defined upper limit. This limit is accessible via <code class="computeroutput">environment::max_tag()</code>.</td> </tr> </tbody> </table></div></td> </tr></tbody> </table></div> </li> <li class="listitem"> <pre class="literallayout">template<typename T> void <a name="idp144481888-bb"></a>send(int dest, int tag, const T * values, int n) const;</pre>Send an array of values to another process. This routine executes a potentially blocking send of an array of data with tag <code class="computeroutput">tag</code> to the process with rank <code class="computeroutput">dest</code>. It can be received by the destination process with a matching array <code class="computeroutput">recv</code> call. If <code class="computeroutput">T</code> is an MPI datatype, an invocation of this routine will be mapped to a single call to MPI_Send, using the datatype <code class="computeroutput">get_mpi_datatype<T>()</code>. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody><tr> <td>Parameters:</td> <td><div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td><code class="computeroutput">dest</code></td> <td>The process rank of the remote process to which the data will be sent.</td> </tr> <tr> <td><code class="computeroutput">n</code></td> <td>The number of values stored in the array. The destination process must call receive with at least this many elements to correctly receive the message. </td> </tr> <tr> <td><code class="computeroutput">tag</code></td> <td>The tag that will be associated with this message. Tags may be any integer between zero and an implementation-defined upper limit. This limit is accessible via <code class="computeroutput">environment::max_tag()</code>.</td> </tr> <tr> <td><code class="computeroutput">values</code></td> <td>The array of values that will be transmitted to the receiver. The type <code class="computeroutput">T</code> of these values must be mapped to an MPI data type.</td> </tr> </tbody> </table></div></td> </tr></tbody> </table></div> </li> <li class="listitem"> <pre class="literallayout">void <a name="idp153555408-bb"></a>send(int dest, int tag) const;</pre>Send a message to another process without any data. This routine executes a potentially blocking send of a message to another process. The message contains no extra data, and can therefore only be received by a matching call to <code class="computeroutput">recv()</code>. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody><tr> <td>Parameters:</td> <td><div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td><code class="computeroutput">dest</code></td> <td>The process rank of the remote process to which the message will be sent.</td> </tr> <tr> <td><code class="computeroutput">tag</code></td> <td>The tag that will be associated with this message. Tags may be any integer between zero and an implementation-defined upper limit. This limit is accessible via <code class="computeroutput">environment::max_tag()</code>. </td> </tr> </tbody> </table></div></td> </tr></tbody> </table></div> </li> <li class="listitem"> <pre class="literallayout">template<typename T> <a class="link" href="status.html" title="Class status">status</a> <a name="idp153560864-bb"></a>recv(int source, int tag, T & value) const;</pre>Receive data from a remote process. This routine blocks until it receives a message from the process <code class="computeroutput">source</code> with the given <code class="computeroutput">tag</code>. The type <code class="computeroutput">T</code> of the <code class="computeroutput">value</code> must be suitable for transmission over MPI, which includes serializable types, types that can be mapped to MPI data types (including most built-in C++ types), packed MPI archives, skeletons, and content associated with skeletons; see the documentation of <code class="computeroutput">send</code> for a complete description. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td>Parameters:</td> <td><div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td><code class="computeroutput">source</code></td> <td>The process that will be sending data. This will either be a process rank within the communicator or the constant <code class="computeroutput">any_source</code>, indicating that we can receive the message from any process.</td> </tr> <tr> <td><code class="computeroutput">tag</code></td> <td>The tag that matches a particular kind of message sent by the source process. This may be any tag value permitted by <code class="computeroutput">send</code>. Alternatively, the argument may be the constant <code class="computeroutput">any_tag</code>, indicating that this receive matches a message with any tag.</td> </tr> <tr> <td><code class="computeroutput">value</code></td> <td>Will contain the value of the message after a successful receive. The type of this value must match the value transmitted by the sender, unless the sender transmitted a packed archive or skeleton: in these cases, the sender transmits a <code class="computeroutput"><code class="computeroutput"><a class="link" href="packed_oarchive.html" title="Class packed_oarchive">packed_oarchive</a></code></code> or <code class="computeroutput"><code class="computeroutput"><a class="link" href="packed_skeleton_oarchive.html" title="Class packed_skeleton_oarchive">packed_skeleton_oarchive</a></code></code> and the destination receives a <code class="computeroutput"><code class="computeroutput"><a class="link" href="packed_iarchive.html" title="Class packed_iarchive">packed_iarchive</a></code></code> or <code class="computeroutput"><code class="computeroutput"><a class="link" href="packed_skeleton_iarchive.html" title="Class packed_skeleton_iarchive">packed_skeleton_iarchive</a></code></code>, respectively.</td> </tr> </tbody> </table></div></td> </tr> <tr> <td>Returns:</td> <td>Information about the received message. </td> </tr> </tbody> </table></div> </li> <li class="listitem"> <pre class="literallayout">template<typename T> <a class="link" href="status.html" title="Class status">status</a> <a name="idp228664608-bb"></a>recv(int source, int tag, const <a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a>< T > & proxy) const;</pre>Receive a skeleton from a remote process. This routine blocks until it receives a message from the process <code class="computeroutput">source</code> with the given <code class="computeroutput">tag</code> containing a skeleton. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td>Parameters:</td> <td><div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td><code class="computeroutput">proxy</code></td> <td>The <code class="computeroutput"><code class="computeroutput"><a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a></code></code> containing a reference to the object that will be reshaped to match the received skeleton.</td> </tr> <tr> <td><code class="computeroutput">source</code></td> <td>The process that will be sending data. This will either be a process rank within the communicator or the constant <code class="computeroutput">any_source</code>, indicating that we can receive the message from any process.</td> </tr> <tr> <td><code class="computeroutput">tag</code></td> <td>The tag that matches a particular kind of message sent by the source process. This may be any tag value permitted by <code class="computeroutput">send</code>. Alternatively, the argument may be the constant <code class="computeroutput">any_tag</code>, indicating that this receive matches a message with any tag.</td> </tr> </tbody> </table></div></td> </tr> <tr> <td>Returns:</td> <td>Information about the received message. </td> </tr> </tbody> </table></div> </li> <li class="listitem"> <pre class="literallayout">template<typename T> <a class="link" href="status.html" title="Class status">status</a> <a name="idp153663552-bb"></a>recv(int source, int tag, <a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a>< T > & proxy) const;</pre>Receive a skeleton from a remote process. This routine blocks until it receives a message from the process <code class="computeroutput">source</code> with the given <code class="computeroutput">tag</code> containing a skeleton. <div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td>Parameters:</td> <td><div class="variablelist"><table border="0" class="variablelist compact"> <colgroup> <col align="left" valign="top"> <col> </colgroup> <tbody> <tr> <td><code class="computeroutput">proxy</code></td> <td>The <code class="computeroutput"><code class="computeroutput"><a class="link" href="skeleton_proxy.html" title="Struct template skeleton_proxy">skeleton_proxy</a></code></code> containing a reference to the object that will be reshaped to match the received skeleton.</td> </tr> <tr> <td><code class="computeroutput">source</code></td> <td>The process that will be sending data. This will either be a process rank within the communicator or the constant <code class="computeroutput">any_source</code>, indicating that we can receive the message from any process.</td> </tr> <tr> <td><code class="computeroutput">tag</code></td> <td>The tag that matches a particular kind of message sent by the source process. This may be any tag value permitted by <code class="computeroutput">send</code>. Alternatively, the argument may be the constant <code class="computeroutput">any_tag</code>, indicating that this receive matches a message with any tag.</td> </tr> </tbody> </table></div></td> </tr> <tr> <td>Returns:</td> <td>Information about the received message. </td> </tr> </tbody> </table></div> </li> <li class="listitem"> <pre class="literallayout">template<typename T> <a class="link" href="status.html" title="Class status">status</a> <a name="idp155663504-bb"></a>recv(int source, int tag, <span c