From 70709c6895a82d6efd7fc77e971a862c6c060421 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Tue, 19 Apr 2011 09:19:33 -0600 Subject: [PATCH] perllocale: Mention /l Also the possibility of an undefined initial locale --- pod/perllocale.pod | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/pod/perllocale.pod b/pod/perllocale.pod index ceb7137..8926d8b 100644 --- a/pod/perllocale.pod +++ b/pod/perllocale.pod @@ -90,7 +90,8 @@ L. =head2 The use locale pragma By default, Perl ignores the current locale. The S> -pragma tells Perl to use the current locale for some operations. +pragma and the C regular expression modifier tell Perl to use the +current locale for some operations (C for just pattern matching). The current locale is set at execution time by L described below. If that function @@ -99,6 +100,8 @@ current locale is that which was determined by the L<"ENVIRONMENT"> in effect at the start of the program, except that C> is always initialized to the C locale (mentioned under L). +If there is no valid environment, the current locale is undefined. It +is likely, but not necessarily, the "C" locale. The operations that are affected by locale are: @@ -950,7 +953,9 @@ always in force, even if the program environment suggested otherwise (see L). By default, Perl still behaves this way for backward compatibility. If you want a Perl application to pay attention to locale information, you B use the S> -pragma (see L) to instruct it to do so. +pragma (see L) or for just pattern matching, the +C regular expression modifier (see L) to instruct it to do so. Versions of Perl from 5.002 to 5.003 did use the C information if available; that is, C<\w> did understand what -- 2.7.4