<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; ">Hi Junchao,<div><br></div><div>Sorry for the delay. I've been at SC.<br><div><br><div><blockquote type="cite"><div dir="ltr">In the MPI_T return code Table (P589), there are <div><br></div><div>Return Codes for Datatype Functions: MPI_T_ENUM_*</div><div><div>MPI_T_ERR_INVALID_INDEX The enumeration index is invalid or has been deleted.</div>
<div>MPI_T_ERR_INVALID_ITEM The item index queried is out of range (for MPI_T_ENUM_GET_ITEM only)</div><div><br></div><div>Why we used "<span style="color:rgb(255,0,0)">enumeration index</span>" here? Since in the standard, it is called a handle. </div></div></div></blockquote><div><br></div>I think the text could better read "enumeration item index" since the index is for an item in the enumeration, not the enumeration itself.</div><div><br><blockquote type="cite"><div dir="ltr"><div><div>And why designed MPI_T_ERR_INVALID_ITEM specially for MPI_T_ENUM_GET_ITEM?</div></div></div></blockquote><div><br></div>I believe the intent was to differentiate between an index that is out of range and one that may have been deleted or invalidated for some reason, which would give more information than just one error code.</div><div><br></div><div>Do others feel this needs changing? If so, what do you think needs to happen? Possibly this:</div><div><br><blockquote type="cite"><div dir="ltr"><div>
<div>In my view, there should be MPI_T_ERR_INVALID_ENUM, MPI_T_ERR_INVALID_INDEX respectively.</div></div></div></blockquote><div><br></div>Or another suggestion:</div><div>return MPI_T_ERR_INVALID_INDEX for indices that are invalid or deleted and MPI_T_ERR_INVALID in the case that the index is out of range. If it's out of range, it's a misuse of the interface, so it fits with the intent of the new return code.<br><div><br></div>Kathryn</div><div><br><blockquote type="cite"><div dir="ltr"><div><div><br clear="all"><div><div dir="ltr">--Junchao Zhang</div></div>
</div></div></div>
_______________________________________________<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 apple-content-edited="true">
<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>______________________________________________________________<br>Kathryn Mohror, <a href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>, <a href="http://people.llnl.gov/mohror1">http://people.llnl.gov/mohror1</a><br>CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA</div><div><br></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br></div></div></body></html>