Bytes in the source text that have their high-bit set will be treated
as being part of a literal UTF-8 character. This includes most
-literals such as identifiers, string constants, constant regular
-expression patterns and package names. On EBCDIC platforms characters
-in the Latin 1 character set are treated as being part of a literal
+literals such as identifier names, string constants, and constant
+regular expression patterns. On EBCDIC platforms characters in
+the Latin 1 character set are treated as being part of a literal
UTF-EBCDIC character.
=back
pre-declaring global symbols, ensuring their availability to the
later-loaded routines.
+The C<use vars> does not work for UTF-8 variable names.
+
See L<perlmodlib/Pragmatic Modules>.
=cut
is now carried with the data, not attached to the operations. (There
is one remaining case where an explicit C<use utf8> is needed: if your
Perl script itself is encoded in UTF-8, you can use UTF-8 in your
-variable and subroutine names, and in your string and regular
-expression literals, by saying C<use utf8>. This is not the default
-because that would break existing scripts having legacy 8-bit data in
-them.)
+identifier names, and in your string and regular expression literals,
+by saying C<use utf8>. This is not the default because that would
+break existing scripts having legacy 8-bit data in them.)
=head2 Perl's Unicode Model