[Mpi-22] Should all constants/types be availablein all languagebindings?

[Supalov, Alexander]

Hi,

If this requirement is to be interpreted literally, then yes, the
standard must define all datatypes in all languages. However, the
example following this statement shows how an MPI_REAL is transformed
into an equivalent C data type. Whether or not this is indeed MPI_REAL
is not clear. It may well be an MPI_FLOAT.

By the way, this example shows that MPI::Fint may be necessary: MPI_Fint
is used here to pass Fortran datatype thru the C function boundary.
Imagine a C++ function. There was a ticket #4 calling for removal of the
MPI::Fint until it was redefined.

Best regards.

Alexander 

-----Original Message-----
From: mpi-22-bounces_at_[hidden]
[mailto:mpi-22-bounces_at_[hidden]] On Behalf Of Hubert Ritzdorf
Sent: Friday, October 24, 2008 6:30 PM
To: MPI 2.2
Subject: Re: [Mpi-22] Should all constants/types be availablein all
languagebindings?

Jeff Squyres wrote:
> You're right, I was not checking 2.1 implementations.
>
> While 2.1 changelog item 2 does specifically mention those constants 
> in all 3 languages, what about the other datatypes? (e.g., MPI_INT vs.

> MPI_INTEGER, etc.?)
>
MPI-2.1 Section 16.3.6 MPI Opaque Objects, page 483, lines 46-47:
"All predefined datatypes can be used in datatype constructors
in any language."
---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.