The last two comments are fine, but I have a problem with the first one. Error codes are only useful if you're still in an application to decode them. If you're aborting, the thing provided to abort should be provided to the user in the form of a return code. That's not useful since it can't be turned into a string, class, etc. anymore.
On Jun 3, 2015, at 6:06 PM, MPI Forum <[email protected]> wrote:
#324: Clarify MPI_ERRORS_ARE_FATAL scope of abort -------------------------------------+------------------------------------- Reporter: jjhursey | Owner: wbland Type: Enhancements to standard | Status: assigned Priority: Forum feedback requested | Milestone: 2015/12/07 Version: MPI <next> | California, USA Keywords: | Resolution: | Implementation status: Waiting -------------------------------------+-------------------------------------
Comment (by bouteill):
page 342 line 40: when the handler aborts processes, the implementation should try to provide an error code which is meaningful for the user, as an example, an error code that can be passed to MPI_ERROR_STRING.
Rationale for the change: easier to read, all error classes are their own error codes, and returning error codes can be more precise. There is no limit on the number of error classes either (MPI_ADD_ERROR_CLASS!)
page 377 line 34: is ---the same as--- the default error handler (remove "the same as")
page 454: Add before the new text: "By default, the predefined error handler for windows handles is MPI_ERRORS_ARE_FATAL". (adapted from FILE chapter wording). Otherwise the default handler on MPI_WIN_NULL is not defined.
-- Ticket URL: <https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/324#comment:17> MPI Forum <https://svn.mpi-forum.org/> MPI Forum