[Mpi3-ft] MPI_Comm_reenable_any_source Alternatives
We have a 30 character limit, and need a better name for MPI_Comm_reenable_any_source. 'reenable' was seen as misleading since some messages are left in the matching queue, and not really 'disabled.' This function is really just a protective handshake with the user so that the MPI library knows that the user has acknowledged the loss of processes. So if we keep the base MPI_Comm__any_source then we have 20 characters. Below are a list of replacement options that I came up with from the old-dusty-thesaurus. Let me know which ones you like best. 20: MPI_Comm__any_source (base) + 5: allow + 7: approve + 5: bless + 7: certify + 5: grant + 6: permit + 6: ratify +10: reactivate + 8: reenable + 8: sanction + 8: validate I kind of like the 'validate' since we are already introducing that concept as a means of confirming with the user a defined behavior. -- Joshua Hursey Postdoctoral Research Associate Oak Ridge National Laboratory http://users.nccs.gov/~jjhursey
participants (1)
-
Josh Hursey