Category talk:MPIF90: Difference between revisions

From Rosetta Code
Content added Content deleted
(mpif90 is not a language to me)
 
m (e (which is and in italian:D) -> and)
Line 1: Line 1:
Isn't this just an utilities to use MPI bindings (or what) for MPI in fortran 90? I mean, the language is still Fortran 90, isn't it? And MPI it's just a library, right? ([http://www.mcs.anl.gov/research/projects/mpi/ MPI project page). I propose to keep simply Fortran 90 e consider MPI as library, without the need to populate with mpicc, mpif90, mpiWhatever, which seem to be just utilities to avoid specifying linking options. --[[User:ShinTakezou|ShinTakezou]] 15:23, 26 July 2009 (UTC)
Isn't this just an utilities to use MPI bindings (or what) for MPI in fortran 90? I mean, the language is still Fortran 90, isn't it? And MPI it's just a library, right? ([http://www.mcs.anl.gov/research/projects/mpi/ MPI project page). I propose to keep simply Fortran 90 and consider MPI as library, without the need to populate with mpicc, mpif90, mpiWhatever, which seem to be just utilities to avoid specifying linking options. --[[User:ShinTakezou|ShinTakezou]] 15:23, 26 July 2009 (UTC)

Revision as of 15:24, 26 July 2009

Isn't this just an utilities to use MPI bindings (or what) for MPI in fortran 90? I mean, the language is still Fortran 90, isn't it? And MPI it's just a library, right? ([http://www.mcs.anl.gov/research/projects/mpi/ MPI project page). I propose to keep simply Fortran 90 and consider MPI as library, without the need to populate with mpicc, mpif90, mpiWhatever, which seem to be just utilities to avoid specifying linking options. --ShinTakezou 15:23, 26 July 2009 (UTC)