summaryrefslogtreecommitdiff
path: root/pod/perlunifaq.pod
diff options
context:
space:
mode:
authorBrian Fraser <fraserbn@gmail.com>2012-01-31 23:42:58 -0300
committerFather Chrysostomos <sprout@cpan.org>2012-06-27 08:49:21 -0700
commit9c98089cc65a0455663dd27e49a0fbc243fbb353 (patch)
treefa9356cd87c1de8cfbd3030cfe42571c61fb9cce /pod/perlunifaq.pod
parentb9cedb1bbe18d1c7805685aefa81dd7be25b51f1 (diff)
downloadperl-9c98089cc65a0455663dd27e49a0fbc243fbb353.tar.gz
perlunifaq: #109408
Diffstat (limited to 'pod/perlunifaq.pod')
-rw-r--r--pod/perlunifaq.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlunifaq.pod b/pod/perlunifaq.pod
index 9bd103c9ac..ca3a180cfd 100644
--- a/pod/perlunifaq.pod
+++ b/pod/perlunifaq.pod
@@ -141,8 +141,8 @@ concern, and you can just C<eval> dumped data as always.
Starting in Perl 5.14 (and partially in Perl 5.12), just put a
C<use feature 'unicode_strings'> near the beginning of your program.
Within its lexical scope you shouldn't have this problem. It also is
-automatically enabled under C<use feature ':5.12'> or using C<-E> on the
-command line for Perl 5.12 or higher.
+automatically enabled under C<use feature ':5.12'> or C<use v5.12> or
+using C<-E> on the command line for Perl 5.12 or higher.
The rationale for requiring this is to not break older programs that
rely on the way things worked before Unicode came along. Those older