Jeff, I like your wording, looks good to me. Are you going to fix up the latex and generate new PDFs that we can send out? -Fab -----Original Message----- From: mpi3-bwcompat-bounces_at_[hidden] [mailto:mpi3-bwcompat-bounces_at_[hidden]] On Behalf Of Jeff Squyres Sent: Sunday, March 13, 2011 7:21 AM To: MPI-3 backwards compatability WG Subject: Re: [Mpi3-bwcompat] MPI Backward Compatibility Working Group On Mar 11, 2011, at 6:06 PM, Solt, David George wrote:

2.5.8 Last sentence change to:

The size of the MPI_Count type is determined by the MPI implementation with the restriction that it must be minimally capable of encoding a C int and Fortran INTEGER and any value that may be stored in an MPI_Aint type.

"...and any value that may be stored in a variable of type MPI_Aint."

Rational thingy:

Rationale. Potatoes. :-)

MPI_Count is used to communicate both the number of elements in a datatype and the bounds of a datatype. The number of elements in a datatype is specified at creation time using a C int or Fortran INTEGER. The bounds may be specified using an MPI_Aint.

This is good. I would change the wording slightly -- let's not use the verb "communicate" here: "MPI_Count explicitly specifies the number of elements in a datatype, and therefore implicitly specifies the bounds of that datatype. The number of elements in a datatype is specified at creation time using a C int or Fortran INTEGER. The extent of a datatype is expressed using an MPI_Aint. How's that? -- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ Mpi3-bwcompat mailing list Mpi3-bwcompat_at_[hidden] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-bwcompat