In many cases MPI names for C functions are of the form
MPI_Class_action_subset. This convention originated with MPI-1. Since MPI-2 an
attempt has been made to standardize the names of MPI functions according to
the following rules. The C++ bindings in particular follow these rules (see
Section C++ Binding Issues
on page C++ Binding Issues
MPI identifiers are limited to 30 characters (31 with the profiling
interface). This is done to avoid exceeding the limit on some
1. In C, all routines associated with a particular type of MPI object
should be of the form MPI_Class_action_subset or, if no subset
exists, of the form MPI_Class_action. In Fortran, all routines
associated with a particular type of MPI object should be of the form
MPI_CLASS_ACTION_SUBSET or, if no subset exists, of the form
MPI_CLASS_ACTION. For C and Fortran we use the C++ terminology
to define the Class. In C++, the routine is a method on
Class and is named MPI::Class::Action_subset.
If the routine is associated with a certain class, but
does not make sense as an object method, it is
a static member function of the class.
C and Fortran names for
some MPI functions (that were defined during the MPI-1 process)
violate these rules
in several cases. The most common exceptions are the omission
of the Class name from the routine and the omission of
the Action where one can be inferred.
2. If the routine is not associated with a class, the name should be of the form MPI_Action_subset in C and MPI_ACTION_SUBSET in Fortran, and in C++ should be scoped in the MPI namespace, MPI::Action_subset.
3. The names of certain actions have been standardized. In particular, Create creates a new object, Get retrieves information about an object, Set sets this information, Delete deletes information, Is asks whether or not an object has a certain property.
Up: Contents Next: Procedure Specification Previous: Document Notation
Return to MPI-2.2 Standard Index
Return to MPI Forum Home Page
(Unofficial) MPI-2.2 of September 4, 2009
HTML Generated on September 10, 2009
MPI identifiers are limited to 30 characters (31 with the profiling interface). This is done to avoid exceeding the limit on some compilation systems.