summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2013-02-19 13:56:20 -0700
committerKarl Williamson <public@khwilliamson.com>2013-02-19 14:12:50 -0700
commit0e18027d899d188a3a156a060d56beb9bfa7ddae (patch)
tree9b2881e0e8ec8a2d8b21184d9e5515eba71eb69b /t
parented35198c46e1299c54bc9728548919ce30ec223d (diff)
downloadperl-0e18027d899d188a3a156a060d56beb9bfa7ddae.tar.gz
re/charset.t, re/fold_grind.t: Note C locale can match 128-255
Craig Berry pointed out that an implementation can have the C locale give meanings to the above-ASCII code points. (I had thought this was an error.) Change label name and comments in these .t files correspondingly.
Diffstat (limited to 't')
-rw-r--r--t/re/charset.t10
-rw-r--r--t/re/fold_grind.t10
2 files changed, 12 insertions, 8 deletions
diff --git a/t/re/charset.t b/t/re/charset.t
index ebbbeb05dd..a1e3be19ff 100644
--- a/t/re/charset.t
+++ b/t/re/charset.t
@@ -45,13 +45,15 @@ if (! is_miniperl() && $Config{d_setlocale}) {
# time, and the one above is run time
use if $Config{d_setlocale}, 'locale';
- # Some locale implementations don't have the 128-255 characters all
- # mean nothing. Skip the locale tests in that situation
+ # Some implementations don't have the 128-255 range characters all
+ # mean nothing under the C locale (an example being VMS). This is
+ # legal, but since we don't know what the right answers should be,
+ # skip the locale tests in that situation.
for my $i (128 .. 255) {
- goto bad_locale if chr($i) =~ /[[:print:]]/;
+ goto untestable_locale if chr($i) =~ /[[:print:]]/;
}
push @charsets, 'l';
- bad_locale:
+ untestable_locale:
}
}
diff --git a/t/re/fold_grind.t b/t/re/fold_grind.t
index d073498bf7..3267336d84 100644
--- a/t/re/fold_grind.t
+++ b/t/re/fold_grind.t
@@ -411,14 +411,16 @@ if($Config{d_setlocale}) {
if ($current_locale eq 'C') {
require locale; import locale;
- # Some locale implementations don't have the range 128-255 characters all
- # mean nothing. Skip the locale tests in that situation.
+ # Some implementations don't have the 128-255 range characters all
+ # mean nothing under the C locale (an example being VMS). This is
+ # legal, but since we don't know what the right answers should be,
+ # skip the locale tests in that situation.
for my $i (128 .. 255) {
my $char = chr($i);
- goto bad_locale if uc($char) ne $char || lc($char) ne $char;
+ goto untestable_locale if uc($char) ne $char || lc($char) ne $char;
}
push @charsets, 'l';
- bad_locale:
+ untestable_locale:
}
}