On Tue, Jun 26, 2012 at 11:41 AM, Douglas Miller <dougmill@us.ibm.com> wrote:

I've got to raise a concern here. If we start defining MPI datatypes to be C++ types then how will an implementation support that with only a C compiler? I thought the point of 281 was to eradicate C++ from the standard (and start over later if C++ was to be defined in the standard).

_______________________________________________
Douglas Miller BlueGene Messaging Development
IBM Corp., Rochester, MN USA Bldg 030-2 A401
dougmill@us.ibm.com Douglas Miller/Rochester/IBM

Jed Brown ---06/26/2012 11:26:16 AM---Jed Brown <jedbrown@mcs.anl.gov>

Jed Brown <jedbrown@mcs.anl.gov>
Sent by: mpi-forum-bounces@lists.mpi-forum.org
06/26/2012 11:14 AM

Please respond to

Main MPI Forum mailing list <mpi-forum@lists.mpi-forum.org>

To

Main MPI Forum mailing list <mpi-forum@lists.mpi-forum.org>,

cc

Subject

Re: [Mpi-forum] C++ types inaccessible after #281

On Tue, Jun 26, 2012 at 6:13 AM, Jeff Squyres <jsquyres@cisco.com> wrote:
There are a few C++-specific datatypes for which it would be worth introducing new C datatypes (e.g., MPI_CXX_COMPLEX). It's too bad that no one realized this until now, because this won't make the MPI-3 deadline. But it could be part of MPI-3.1 or errata, or some such.

Two people in offline discussions have suggested that C bindings to the std::complex types (I'm not aware of anything else that #281 will lose) might qualify as ticket 0._______________________________________________ mpi-forum mailing list mpi-forum@lists.mpi-forum.orghttp://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

_______________________________________________
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

--
Jeff Hammond
Argonne Leadership Computing Facility
University of Chicago Computation Institute
jhammond@alcf.anl.gov / (630) 252-5381
http://www.linkedin.com/in/jeffhammond
https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond