I gotta agree. One reason that we should not require or endorse any
particular thread syntax, and instead focus on the semantics as we have
been doing, is that for MPI, the semantics is the point. To make this
explicit, one can envisage a system that has a POSIX-compliant pthread package
that does *NOT* follow the rules in our "MPI and Threads" discussion, but also
has another thread package that does do so. Then the programmer must not
use pthreads, but the threads that work well with MPI. The program might
not be as portable as it was before the programmer introduced explicit
multithreading, but that is the fault of the threads packages, not MPI.
Rusty