On Tue, 30 Oct 2012, Kirk, Benjamin (JSC-EG311) wrote: >> As long as I'm asking about Parallel:: design decisions - what's the >> intended usage for the DataType argument to our methods which take >> containers-of-T? I understand that for non-built-in types we need to >> tell MPI how to send them, but that can be done by specializing >> StandardType<T>. It seems like an input data type would only be >> useful if you wanted to be able to communicate the same C++-type as >> multiple *different* MPI types. > > AFAICT is is because the DataType argument preceded the > StandardType<T>. I'm honestly having a hard time finding code that > uses the input DataType?
I remember replacing a couple invocations that used the input DataType with code that specialized the StandardType; didn't know I'd replaced them *all*. I'm considering deprecating the input DataType method versions, but I'm very wary of taking something like that away if there's a use case I just didn't think of... --- Roy ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
