summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorKarl Williamson <khw@cpan.org>2016-08-08 15:28:10 -0600
committerKarl Williamson <khw@cpan.org>2016-08-08 15:30:51 -0600
commit904cefa8028c48db3b11b95124c356edb7f12b5d (patch)
tree05e8ee629a3ba69c0848bc1a5616113a3600e041 /pod
parentaeb72ccb42732a816ef2710b4141236752cc535f (diff)
downloadperl-904cefa8028c48db3b11b95124c356edb7f12b5d.tar.gz
perldiag: YA case of too large code point breakage
This adds another case where having a code point above IV_MAX doesn't work properly, and stresses there may be more.
Diffstat (limited to 'pod')
-rw-r--r--pod/perldiag.pod5
1 files changed, 4 insertions, 1 deletions
diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index 2b16b30f50..6c13a32dcc 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -6900,7 +6900,10 @@ points up to 0x10FFFF, but Perl allows much larger ones. However, the
largest possible ones break the perl interpreter in some constructs,
including causing it to hang in a few cases. The known problem areas
are in C<tr///>, regular expression pattern matching using quantifiers,
-and as the upper limits in loops.
+as quote delimiters in C<qI<X>...I<X>> (where I<X> is the C<chr()> of a large
+code point), and as the upper limits in loops.
+There may be other breakages as well. If you get this warning, and
+things aren't working correctly, you probably have found one of these.
If your code is to run on various platforms, keep in mind that the upper
limit depends on the platform. It is much larger on 64-bit word sizes