summaryrefslogtreecommitdiff
path: root/pod/perlfunc.pod
diff options
context:
space:
mode:
authorJames E Keenan <jkeenan@cpan.org>2019-05-26 22:30:40 -0400
committerJames E Keenan <jkeenan@cpan.org>2019-05-30 19:03:28 -0400
commitda5a0da22ef5f5dd64e1fcdcac2c5ed1c0398085 (patch)
treefa96c0d6d17bf75bade4cd95a3585c50978f2de0 /pod/perlfunc.pod
parentc57372c9fa47e84c987c5804e5247ef5aea9a02d (diff)
downloadperl-da5a0da22ef5f5dd64e1fcdcac2c5ed1c0398085.tar.gz
Use of strings with code points over 0xFF as arguments to "vec"
Implement scheduled fatalization. Adapt existing tests in t/op/vec.t. Eliminate t/lib/warnings/doop and move one test to t/op/vec.t. Document this fatalization in perldiag and perlfunc. Documentation improvement recommended by Karl Williamson. For: RT # 134139
Diffstat (limited to 'pod/perlfunc.pod')
-rw-r--r--pod/perlfunc.pod6
1 files changed, 2 insertions, 4 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 196a88d71f..0e50132907 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -9669,10 +9669,8 @@ to try to write off the beginning of the string (i.e., negative OFFSET).
If the string happens to be encoded as UTF-8 internally (and thus has
the UTF8 flag set), L<C<vec>|/vec EXPR,OFFSET,BITS> tries to convert it
to use a one-byte-per-character internal representation. However, if the
-string contains characters with values of 256 or higher, that conversion
-will fail, and a deprecation message will be raised. In that situation,
-C<vec> will operate on the underlying buffer regardless, in its internal
-UTF-8 representation. In Perl 5.32, this will be a fatal error.
+string contains characters with values of 256 or higher, a fatal error
+will occur.
Strings created with L<C<vec>|/vec EXPR,OFFSET,BITS> can also be
manipulated with the logical