I proposed, that we could omit MPI_SPAWN, because its function
is identical with MPI_SPAWN_MULTIPLE(...count=1...).
Due to a probably FALSE argument, this proposal was thrown away:
The argument was:
In Fortran 77 it is not possible to use a string as an
actual argument if the formal argument is an array of strings.
I tested the following example - but I have no Fortran 77 standard
document to decide if the argument is definitely false.
character*7 s, c(5)
s = 'string-xyz'
do 1, i=1,n
write(*,*) len(c),len(c(i)),' -> ',c(i)
Is this example correct in Fortran 77?
Can someone answer this question?
Are there reasons from the C viewpoint to leave MPI_SPAWN in the
Are there other reasons?
If the example is correct and if there are no other reasons
then we do not need MPI_SPAWN, MPI_ISPAWN, ... and we can
rename MPI_..._MULTIPLE_::: into MPI_..._:::.
According to the message
> Date: Mon, 29 Apr 1996 18:08:08 -0400
> From: Gary Oberbrunner <firstname.lastname@example.org>
> Subject: Dynamic Process comment: using MPI_Init() without mpirun
> I have to say the dynamic process stuff is really shaping up nicely.
> I look forward to using it. There are too many functions, of course,
> but that can't be helped except by collapsing them and adding extra
> args, which I think had been rejected before. Of course MPI_Spawn is
> just MPI_Spawn_Multiple with count=1, and all of the Spawns are really
> spawn_independent with accept & connect, but I'd still keep them
> because they're convenient (even though they're trivial to implement
> using the other functions, right?)
Rolf Rabenseifner (Computer Center )
Rechenzentrum Universitaet Stuttgart (University of Stuttgart)
Allmandring 30 Phone: ++49 711 6855530
D-70550 Stuttgart 80 FAX: ++49 711 6787626