MPI_COMM_PARENT, etc

William Saphir (wcs@nersc.gov)
Mon, 14 Apr 1997 22:43:59 -0700 (PDT)

A while ago Nick pointed out that MPI_COMM_PARENT has a problem
because it is a constant, but we would like to be able to give it to
MPI_COMM_DISCONNECT.

There's been no discussion on this, so I've picked one of the proposed
solutions and brought back MPI_COMM_GET_PARENT. The text should be
checked to make sure there are no problems.

I expect this to be the only nontrivial change in the dynamic chapter.
There will be lots of small binding changes, mostly to come into
conformance on the C++ side.

The function name changes, which will not be accompanied by
change bars (there are too many) are:

MPI_SPAWN MPI_COMM_SPAWN
MPI_SPAWN_MULTIPLE MPI_COMM_SPAWN_MULTIPLE
MPI_ACCEPT MPI_COMM_ACCEPT
MPI_CONNECT MPI_COMM_CONNECT
MPI_JOIN MPI_COMM_JOIN
MPI_NAMESERVICE_LOOKUP_NAME MPI_LOOKUP_NAME
MPI_NAMESERVICE_DELETE_NAME MPI_DELETE_NAME
MPI_NAMESERVICE_PUBLISH_NAME MPI_PUBLISH_NAME

The last three are motivated by the nonexistence of a "nameserver"
class/handle. I personally like the cleaner scoping of the original
names, but consistency says otherwise.

Bill