that 32 ompi/include/mpif-externals.h ! Note that MPI_CONVERSION_FN_NULL is a "constant" (it is only ever that 33 ompi/include/mpif-sentinels.h ! that we already have overloaded F90 bindings for all available that 38 ompi/include/mpif-sentinels.h ! Making MPI_ARGV_NULL be the same type as the parameter that is that 39 ompi/include/mpif-sentinels.h ! exepected in the F90 binding for MPI_COMM_SPAWN means that we that 45 ompi/include/mpif-sentinels.h ! F77 functions are all smart enough to check that the errcodes that 47 ompi/include/mpif-sentinels.h ! (hence, the fact that this is an array of only 1 element does not that 24 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! the ones prototyped in this file) are simple routines that simply that 43 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! Fortran interface so that the compiler can verify that we're passing that 47 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! MPI_Alltoallw), we declare that the corresponding ompi_*_f() that 53 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! However, remember that Fortran passes by reference. So the compiler that 64 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! The key here is that there is a disconnect between Fortran and C: that 68 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! Yes, this is a total hack. But Craig Rasumussen tells me that this that 79 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! was cleverly designed so that it can be identical (in terms of a that 85 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! an "interface" block for the PMPI_* subroutine that we want to call. that 86 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! And we lie in that interface block, saying that the status argument that 89 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! the same type that we already have. that 115 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! The main difference here is that in Fortran, it is an error -- not a that 124 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! Wasn't that simple? Here's the list of subroutines that are not that 195 ompi/mpi/fortran/use-mpi-f08/bindings/mpi-f-interfaces-bind.h ! Note that we have an F08-specific C implementation function for that 10 ompi/mpi/fortran/use-mpi-tkr/mpi-f90-cptr-interfaces.h ! This file contains interfaces that use the ISO_C_BINDING module and that 12 ompi/mpi/fortran/use-mpi-tkr/pmpi-f90-cptr-interfaces.h ! This file contains interfaces that use the ISO_C_BINDING module and that 12 ompi/mpiext/example/use-mpi-f08/mpiext_example_usempif08.h ! section. Note that the extension's mpif.h file will be included that 17 ompi/mpiext/example/use-mpi-f08/mpiext_example_usempif08.h ! here. Note that the mpiext_example_mpif.h will automatically be that 12 ompi/mpiext/example/use-mpi/mpiext_example_usempi.h ! section. Note that the extension's mpif.h file will be included that 17 ompi/mpiext/example/use-mpi/mpiext_example_usempi.h ! here. Note that the mpiext_example_mpif.h will automatically be that 15 ompi/mpiext/pcollreq/use-mpi-f08/mpiext_pcollreq_usempif08.h ! section. Note that the extension's mpif.h file will be included that 20 ompi/mpiext/pcollreq/use-mpi-f08/mpiext_pcollreq_usempif08.h ! here. Note that the mpiext_example_mpif.h will automatically be that 15 ompi/mpiext/pcollreq/use-mpi/mpiext_pcollreq_usempi.h ! section. Note that the extension's mpif.h file will be included that 20 ompi/mpiext/pcollreq/use-mpi/mpiext_pcollreq_usempi.h ! here. Note that the mpiext_example_mpif.h will automatically be