Subject: New issue: MPI::Datatype Set_attr & Set_name
To: mpi-21@XXXXXXXXXXXXX
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
From: "Richard Treumann" <treumann@XXXXXXXXXX>
Date: Wed, 13 Jun 2001 22:40:35 -0400
X-MIMETrack: Serialize by Router on D01ML077/01/M/IBM(Release 5.0.7a SPR #MIAS4UTJ8H, S/390
 SPR #JHEG4V8UT5 & S/390 SPR #JHEG4WERGL |May 21, 2001) at 06/13/2001 10:41:40
 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mpi-21@XXXXXXXXXXXXX
Precedence: bulk
Reply-To: mpi-21@XXXXXXXXXXXXX


The MPI C++ bindings state that the predefined datatypes have form:

const MPI::Datatype MPI::CHAR(MPI_CHAR)

But making predefined MPI_Datatypes "const" has the effect of preventing
either:
INT::Set_attr( key, attribute) or INT::Set_name( string );      from
working.

Page 179:5-8 says that "default" names on communicators like MPI_COMM_WORLD
can be replaced and page 180:19-21 refers to "default" names on predefined
datatypes.  I interpret this as allowing "default" names on predefined
datatypes to also be replaced.

I see no reason to prohibit either of the following:

INT::Set_attr( key, attribute) or INT::Set_name( string );

I am not a C++ expert so fire away if I am missing something important.
Based on what I see though, I suggest eliminating "const" from the
predefined datatype declarations.

            Dick

Dick Treumann                RS/6000 SP Development
IBM Poughkeepsie Unix Development Lab
Dept 0lva / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601
Tele (845) 433-7846         Fax (845) 433-8363