On May 24, 2016, at 7:19 AM, Siegmar Gross <siegmar.gr...@informatik.hs-fulda.de> wrote: > > I don't see a difference for my spawned processes, because both functions will > "wait" until all pending operations have finished, before the object will be > destroyed. Nevertheless, perhaps my small example program worked all the years > by chance.
FWIW: COMM_DISCONNECT is (effectively) used to guarantee that a communicator is destroyed. It can actually be used with any communicator (other than COMM_WORLD and COMM_SELF), but is typically used with communicators created by CONNECT, ACCEPT, JOIN, SPAWN, or SPAWN_MULTIPLE. When used with a communicator that was created by the dynamic operations (e.g., SPAWN), it effectively "disconnects" the two groups in the communicator that it just freed (assuming that that communicator was the only one spanning the two groups). -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
