diff options
author | Karl Williamson <khw@cpan.org> | 2017-06-07 13:31:10 -0600 |
---|---|---|
committer | Karl Williamson <khw@cpan.org> | 2017-06-07 15:05:17 -0600 |
commit | fac71630f045e7ab325b37548d59b6558735e5c3 (patch) | |
tree | d2e968739c55a460cb0f12e9a942ffee976dbd71 /pod/perlunicode.pod | |
parent | 55951dd7f3503c21c2f34146e50e6411317fd1b2 (diff) | |
download | perl-fac71630f045e7ab325b37548d59b6558735e5c3.tar.gz |
Update pods about bitwise UTF-8 above 0xFF being fatal
Diffstat (limited to 'pod/perlunicode.pod')
-rw-r--r-- | pod/perlunicode.pod | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod index 9c13c35a9c..43f145918b 100644 --- a/pod/perlunicode.pod +++ b/pod/perlunicode.pod @@ -191,11 +191,12 @@ C<scalar reverse()> reverses by character rather than by byte. =item * The bit string operators, C<& | ^ ~> and (starting in v5.22) -C<&. |. ^. ~.> can operate on characters that don't fit into a byte. -However, the current behavior is likely to change. You should not use -these operators on strings that are encoded in UTF-8. If you're not -sure about the encoding of a string, downgrade it before using any of -these operators; you can use +C<&. |. ^. ~.> can operate on bit strings encoded in UTF-8, but this +can give unexpected results if any of the strings contain code points +above 0xFF. Starting in v5.28, it is a fatal error to have such an +operand. Otherwise, the operation is performed on a non-UTF-8 copy of +the operand. If you're not sure about the encoding of a string, +downgrade it before using any of these operators; you can use L<C<utf8::utf8_downgrade()>|utf8/Utility functions>. =back |