In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/904cefa8028c48db3b11b95124c356edb7f12b5d?hp=aeb72ccb42732a816ef2710b4141236752cc535f>
- Log ----------------------------------------------------------------- commit 904cefa8028c48db3b11b95124c356edb7f12b5d Author: Karl Williamson <[email protected]> Date: Mon Aug 8 15:28:10 2016 -0600 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. ----------------------------------------------------------------------- Summary of changes: pod/perldiag.pod | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pod/perldiag.pod b/pod/perldiag.pod index 2b16b30..6c13a32 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 -- Perl5 Master Repository
