From 8262de4c7073e33d1bb29f3e9b54b69c8686af6e Mon Sep 17 00:00:00 2001 From: David Solt Date: Mon, 18 Sep 2023 11:27:24 -0500 Subject: [PATCH] Better wording of advise on user defined event codes Co-authored-by: Aurelien Bouteiller --- Chap_API_Event.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Chap_API_Event.tex b/Chap_API_Event.tex index e3b73b8..db1ccd9 100644 --- a/Chap_API_Event.tex +++ b/Chap_API_Event.tex @@ -149,7 +149,7 @@ \subsection{\code{PMIx_Register_event_handler}} Register an event handler to report events. Note that the codes being registered do \textit{not} need to be \ac{PMIx} event constants --- any integer value can be registered. This allows for registration of non-PMIx events such as those defined by a particular \ac{SMS} vendor or by an application itself. \adviceuserstart -In order to avoid potential conflicts, users are advised to only use values as event codes if they lie outside the range of the \ac{PMIx} standard's error and event codes (See \ref{api:struct:usererrors}). Thus, \ac{SMS} vendors and application developers should constrain their definitions to positive values or negative values beyond the \refconst{PMIX_EXTERNAL_ERR_BASE} boundary. +In order to avoid potential conflicts, users are advised to only use event code values that lie outside the range of the \ac{PMIx} standard's error and event codes (See \ref{api:struct:usererrors}). Thus, \ac{SMS} vendors and application developers should constrain their definitions to positive values or negative values beyond the \refconst{PMIX_EXTERNAL_ERR_BASE} boundary. \adviceuserend