<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br><div><div>On Feb 15, 2014, at 4:47 AM, Marc-Andre Hermanns <<a href="mailto:m.a.hermanns@grs-sim.de">m.a.hermanns@grs-sim.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">+1<br><br>I under stand the null-terminating character as "the character doing the<br>null termination". As only the null character can do that, the text is<br>clearer now.<br><br>Cheers,<br>Marc-Andre<br><br>On 15.02.14 13:42, Jeff Squyres (jsquyres) wrote:<br><blockquote type="cite">Sorry -- nit-picking on my own text:<br><br>-----<br>The use of the datatype MPI_CHAR in the MPI tool information interface implies a null-terminated character array, i.e., a string in the C language. If a variable has type MPI_CHAR, the value of the count parameter returned by MPI_T_CVAR_HANDLE_ALLOC and MPI_T_PVAR_HANDLE_ALLOC must be large enough to include any valid value, including its null-terminating character. The contents of returned MPI_CHAR arrays are only defined from index 0 through the location of the first null-terminating character.<br>-----<br><br>In the 2nd and 3rd sentence, we refer to the "null-terminating character". Is that correct? Isn't it just a "null character"?<br><br>We use "null-terminated character array" in the first sentence, and that seems fine. But "null-terminated character" means "a character terminated by a null", which doesn't seem to make sense.<br><br>In 14.3.3 ("Convention for Returning Strings"), we refer to the "null terminator" and "terminating null character"). <br><br>I therefore think we should slightly change the last 2 sentences to:<br><br>-----<br>The use of the datatype MPI_CHAR in the MPI tool information interface implies a null-terminated character array, i.e., a string in the C language. If a variable has type MPI_CHAR, the value of the count parameter returned by MPI_T_CVAR_HANDLE_ALLOC and MPI_T_PVAR_HANDLE_ALLOC must be large enough to include any valid value, including its ***terminating null*** character. The contents of returned MPI_CHAR arrays are only defined from index 0 through the location of the first ***null*** character.<br>-----<br><br><br><br><br>On Feb 14, 2014, at 6:16 PM, "Mohror, Kathryn" <<a href="mailto:mohror1@llnl.gov">mohror1@llnl.gov</a>> wrote:<br><br><blockquote type="cite">Thanks for the feedback. I have attached a new draft for this ticket and incorporated your changes. Please give me any additional comments by the start of business Monday.<br><br>Kathryn<br><br>On Feb 14, 2014, at 7:23 AM, Dave Goodell (dgoodell) <<a href="mailto:dgoodell@cisco.com">dgoodell@cisco.com</a>> wrote:<br><br><blockquote type="cite">+1 to almost everything that Jeff said. My only quibble would be to change the last sentence in his text from:<br><br>The contents of returned MPI_CHAR values are only defined from index 0 through the location of the first null-terminating character.<br><br>To:<br><br>The contents of returned MPI_CHAR ***arrays*** are only defined from index 0 through the location of the first null-terminating character.<br><br>-Dave<br><br>On Feb 14, 2014, at 7:27 AM, Jeff Squyres (jsquyres) <<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>> wrote:<br><br><blockquote type="cite">Here's the new text:<br><br>-----<br>The use of the datatype MPI_CHAR in the MPI tool information interface implies a null-terminated character array, i.e. a string in the C language. If a variable has type MPI_CHAR, the value of the count parameter returned by MPI_T_CVAR_HANDLE_ALLOC and MPI_T_PVAR_HANDLE_ALLOC will include the null-terminating character. The value returned in count must be large enough to contain any valid value for the given variable. Arrays of type MPI_CHAR are only valid to the first null character.<br>-----<br><br>There's a missing "," after "i.e." -- it should be "i.e.,"<br><br>I'd make some other minor changes:<br><br>The use of the datatype MPI_CHAR in the MPI tool information interface implies a null-terminated character array, i.e., a string in the C language. If a variable has type MPI_CHAR, the value of the count parameter returned by MPI_T_CVAR_HANDLE_ALLOC and MPI_T_PVAR_HANDLE_ALLOC ***must be large enough to include any valid value, including its null-terminating character.*** ***The contents of returned MPI_CHAR values are only defined from index 0 through the location of the first null-terminating character.***<br><br><br><br><br><br>On Feb 13, 2014, at 3:24 PM, Kathryn Mohror <<a href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>> wrote:<br><br><blockquote type="cite">Hi all,<br><br>Please have a look at this since we have to decide if it's ready for a reading, and submit it to the forum for review on Monday if we do.<br><br>Kathryn<br><br>On Feb 7, 2014, at 1:05 PM, "Mohror, Kathryn" <<a href="mailto:mohror1@llnl.gov">mohror1@llnl.gov</a>> wrote:<br><br><blockquote type="cite">Hi all,<br><br>As we discussed in our call, I have drafted new text for ticket 405 which clarifies our intent for the MPI_CHAR datatype to represent strings in the tools interface. Please take a look at the red text for ticket 405 in the attached document and send your comments.<br><br>Kathryn<br><br><br>_________________________________________________________________<br>Kathryn Mohror, <a href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>, <a href="http://scalability.llnl.gov/">http://scalability.llnl.gov/</a><br>Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA<br><br><br><br><br><br><br><br><br><tools-3.pdf>_______________________________________________<br>mpiwg-tools mailing list<br><a href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a><br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools<br></blockquote><br>_________________________________________________________________<br>Kathryn Mohror, <a href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>, <a href="http://scalability.llnl.gov/">http://scalability.llnl.gov/</a><br>Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA<br><br><br><br><br><br><br><br><br>_______________________________________________<br>mpiwg-tools mailing list<br><a href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a><br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools<br></blockquote><br><br>-- <br>Jeff Squyres<br><a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a><br>For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/<br><br>_______________________________________________<br>mpiwg-tools mailing list<br>mpiwg-tools@lists.mpi-forum.org<br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools<br></blockquote><br>_______________________________________________<br>mpiwg-tools mailing list<br><a href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a><br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools<br></blockquote><br>_________________________________________________________________<br>Kathryn Mohror, <a href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>, <a href="http://scalability.llnl.gov/">http://scalability.llnl.gov/</a><br>Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA<br><br><br><br><br><br><br><br><br><tools-3.pdf>_______________________________________________<br>mpiwg-tools mailing list<br><a href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a><br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools<br></blockquote><br><br></blockquote><br>-- <br>Marc-Andre Hermanns<br>German Research School for<br>Simulation Sciences GmbH<br>c/o Laboratory for Parallel Programming<br>52062 Aachen | Germany<br><br>Tel +49 241 80 99753<br>Fax +49 241 80 6 99753<br>Web <a href="http://www.grs-sim.de">www.grs-sim.de</a><br><br>Members: Forschungszentrum Jülich GmbH | RWTH Aachen University<br>Registered in the commercial register of the local court of<br>Düren (Amtsgericht Düren) under registration number HRB 5268<br>Registered office: Jülich<br>Executive board: Prof. Marek Behr, Ph.D | Prof. Dr. Sebastian M. Schmidt<br><br>_______________________________________________<br>mpiwg-tools mailing list<br><a href="mailto:mpiwg-tools@lists.mpi-forum.org">mpiwg-tools@lists.mpi-forum.org</a><br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools</blockquote></div><br><div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>_________________________________________________________________</div><div>Kathryn Mohror, <a href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>, <a href="http://scalability.llnl.gov/">http://scalability.llnl.gov/</a><br>Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA<br></div><div><br></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><br class="Apple-interchange-newline">
</div>
<br></div></body></html>