[mpiwg-tools] proposed text
kathryn at llnl.gov
Tue Nov 18 14:25:55 CST 2014
I'm a bit lost on the intended meaning behind the name: <foo> strings.
Do you want <foo> strings to indicate all strings in the MPI tool
information interface that are by our definition in 14.3.3 treated
differently than in the rest of the standard? And then have a concept of
identical <foo> strings and specify what is returned in the user's buffer
for identical <foo> strings?
Or is <foo> strings supposed to only indicate strings that if identical,
have a particular defined behavior that determine what is returned into
the user's buffer according to our string conventions in 14.3.3?
>>> - so up in 14.3.3, have a definition for "<foo> strings" (someone come
>>> with a better name than "<foo>"):
>> MPI_T strings?
>Mmm. That would imply that these are the *only* type of strings that are
>used in MPI_T. That may be true today, but I don't know if we want to be
>locked in to that generalization for forever.
>How about "MPI_T universal strings"?
>jsquyres at cisco.com
>For corporate legal information go to:
>mpiwg-tools mailing list
>mpiwg-tools at lists.mpi-forum.org
More information about the mpiwg-tools