From e8c3ef4a2a5c08a4c5f3fa7e6d4cda579068adbd Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Mon, 28 Mar 2022 13:25:10 -0600 Subject: [PATCH] perllocale: Add note about z/OS special behavior --- pod/perllocale.pod | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/pod/perllocale.pod b/pod/perllocale.pod index 7a93419..932a9ef 100644 --- a/pod/perllocale.pod +++ b/pod/perllocale.pod @@ -415,10 +415,13 @@ expecting. On some platforms, there can be a race leading to segfaults if two threads call this function nearly simultaneously. This warning does not apply on unthreaded builds, or on perls where C<${^SAFE_LOCALES}> exists and is non-zero; namely Perl 5.28 and later -unthreaded or compiled to be locale-thread-safe. +unthreaded or compiled to be locale-thread-safe. On z/OS systems, this +function becomes a no-op once any thread is started. Thus, on that +system, you can set up the locale before creating any threads, and that +locale will be the one in effect for the entire program. -You can switch locales as often as you wish at run time with the -C function: +Otherwise, you can switch locales as often as you wish at run time with +the C function: # Import locale-handling tool set from POSIX module. # This example uses: setlocale -- the function call -- 1.8.3.1