summaryrefslogtreecommitdiff
path: root/pod/perlebcdic.pod
diff options
context:
space:
mode:
authorKarl Williamson <khw@cpan.org>2015-05-08 22:15:25 -0600
committerKarl Williamson <khw@cpan.org>2015-05-08 22:18:35 -0600
commit416c06fc852c00a948ade2fd39e7bf1b9f00ca9d (patch)
tree2824123fa32f303b8a2624f1fd515419f462a4c2 /pod/perlebcdic.pod
parentf6cf462769452c3cb33bad43544b1e536d797585 (diff)
downloadperl-416c06fc852c00a948ade2fd39e7bf1b9f00ca9d.tar.gz
perlebcdic: Document v5.22 EBCDIC bugs
Diffstat (limited to 'pod/perlebcdic.pod')
-rw-r--r--pod/perlebcdic.pod16
1 files changed, 16 insertions, 0 deletions
diff --git a/pod/perlebcdic.pod b/pod/perlebcdic.pod
index c1d8c85460..d88291ae64 100644
--- a/pod/perlebcdic.pod
+++ b/pod/perlebcdic.pod
@@ -1842,6 +1842,22 @@ XXX.
=item *
+The C<cmp> (and hence C<sort>) operators do not necessarily give the
+correct results when both operands are UTF-EBCDIC encoded strings and
+there is a mixture of ASCII and/or control characters, along with other
+characters.
+
+=item *
+
+Ranges containing C<\N{...}> in the C<tr///> (and C<y///>)
+transliteration operators are treated differently than the equivalent
+ranges in regular expression pattersn. They should, but don't, cause
+the values in the ranges to all be treated as Unicode code points, and
+not native ones. (L<perlre/Version 8 Regular Expressions> gives
+details as to how it should work.)
+
+=item *
+
Not all shells will allow multiple C<-e> string arguments to perl to
be concatenated together properly as recipes in this document
0, 2, 4, 5, and 6 might