No reason for doing so comes to mind - I suspect the original author probably
started out doing a "free", then discovered that the overlying MPI code was
passing in an array and so just converted it to a memset. Either way, it really
should be the responsibility of the user's code to deal with t
Dear All,
Next is question about "MPI_Close_port".
According to the MPI-2.2 standard,
the "port_name" argument of
MPI_Close_port() is marked as 'IN'.
But, in Open MPI (both trunk and 1.4.x), the content of
"port_name" is updated in MPI_Close_port().
It seems to violate the MPI standard.
The foll
