Jed,
On 2/10/2016 12:18 AM, Jed Brown wrote:
Did anyone suggest violating the standard?
if i understand correctly what George wrote earlier, then yes, removing
predefined datatypes from the header files can be seen as a violation of
the standard
in your configure script, you can simply try to compile a simple fortran
MPI hello world.
if it fails, then you can assume fortran bindings are not available, and
not use fortran types in your application.
With which compiler? Remember that we're talking about the C macros --
the user of those might not have any Fortran in their code. Like
suppose I have a C library that implements a custom reduction. I'll
need to be checking the datatype to dispatch to a concrete
implementation. Must I compile in support for being called with
MPI_DOUBLE_COMPLEX?
does that really matter ?
i assume your library and the user code are built with the same OpenMPI.
if there is no Fortran support, then you are compiling code that cannot
be invoked (e.g. dead code),
and though that is not the most elegant thing to do, that does not sound
like a showstopper to me.
so yes, compile in support for being called with Fortran predefined
datatypes,
worst case scenario is you generate broken dead code.
Cheers,
Gilles
