On 05/20/2013 08:55 AM US Central Time, Jeff Squyres (jsquyres) wrote:

On May 20, 2013, at 9:52 AM, Pavan Balaji <[email protected]> wrote:

...

As nasty as it is, apart from implementation difficulty, what's the problem with it in the standard (apart from wording clarification)?

The standard doesn't say what you're allowed (or not allowed) to do at all.

Yes, I'm looking at this as wording clarification. Right now, since the standard doesn't disallow it, applications use it as if it's allowed.

For example, can you call MPI_SEND from within an attribute call back? Or MPI_COMM_SPAWN?

Yes to both.

And what about the non-deterministic effects that I called out in the email back in 2011 -- are those allowed, and if so, do we need to say that they're non-deterministic? ...and so on.-

Right, we did talk about the non-determinism on this email thread before you joined in, but we concluded that there's only one sensible way. Of course, that should be clarified in the standard. But it's not a major change in implementations, I think. -- Pavan - Pavan Balaji http://www.mcs.anl.gov/~balaji