summaryrefslogtreecommitdiff
path: root/pod/perlop.pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2001-02-28 16:22:26 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2001-02-28 16:22:26 +0000
commit945c54fd8d2501611a8e97dae49e901ff9478cad (patch)
treee7be4ebc0dbd9964ba352f90cf3c58042fb44318 /pod/perlop.pod
parent494f3023e6cb99f0f26ded70a0869fe24d04973e (diff)
downloadperl-945c54fd8d2501611a8e97dae49e901ff9478cad.tar.gz
Undo qu. Retract #8814, rewrite op/each part of #8615,
retract toke.c/qu parts of #8583, retract #8485, retract or rewrite qu parts of #8439 of toke.c, keywords.h, keywords.pl, op/length.t, and MANIFEST, and delete t/op/qu.t. p4raw-id: //depot/perl@8967
Diffstat (limited to 'pod/perlop.pod')
-rw-r--r--pod/perlop.pod70
1 files changed, 27 insertions, 43 deletions
diff --git a/pod/perlop.pod b/pod/perlop.pod
index 2bc889d186..8f2ecde031 100644
--- a/pod/perlop.pod
+++ b/pod/perlop.pod
@@ -645,7 +645,6 @@ any pair of delimiters you choose.
Customary Generic Meaning Interpolates
'' q{} Literal no
"" qq{} Literal yes
- qu{} Literal yes (UTF-8, see below)
`` qx{} Command yes (unless '' is delimiter)
qw{} Word list no
// m{} Pattern match yes (unless '' is delimiter)
@@ -1012,48 +1011,6 @@ Options are:
See L<perlre> for additional information on valid syntax for STRING, and
for a detailed look at the semantics of regular expressions.
-=item qw/STRING/
-
-Evaluates to a list of the words extracted out of STRING, using embedded
-whitespace as the word delimiters. It can be understood as being roughly
-equivalent to:
-
- split(' ', q/STRING/);
-
-the difference being that it generates a real list at compile time. So
-this expression:
-
- qw(foo bar baz)
-
-is semantically equivalent to the list:
-
- 'foo', 'bar', 'baz'
-
-Some frequently seen examples:
-
- use POSIX qw( setlocale localeconv )
- @EXPORT = qw( foo bar baz );
-
-A common mistake is to try to separate the words with comma or to
-put comments into a multi-line C<qw>-string. For this reason, the
-C<use warnings> pragma and the B<-w> switch (that is, the C<$^W> variable)
-produces warnings if the STRING contains the "," or the "#" character.
-
-=item qu/STRING/
-
-Like L<qq> but explicitly generates UTF-8 from the \0ooo, \xHH, and
-\x{HH} constructs if the code point is in the 0x80..0xff range (and
-of course for the 0x100.. range).
-
-Normally you do not need to use this because whether characters are
-internally encoded in UTF-8 should be transparent, and you can just
-just use qq, also known as "".
-
-(In qq/STRING/ the \0ooo, \xHH, and the \x{HHH...} constructs
-generate bytes for the 0x80..0xff range. For the whole 0x00..0xff
-range the generated bytes are host-dependent: in ISO 8859-1 they will
-be ISO 8859-1, in EBCDIC they will EBCDIC, and so on.)
-
=item qx/STRING/
=item `STRING`
@@ -1135,6 +1092,33 @@ Just understand what you're getting yourself into.
See L<"I/O Operators"> for more discussion.
+=item qw/STRING/
+
+Evaluates to a list of the words extracted out of STRING, using embedded
+whitespace as the word delimiters. It can be understood as being roughly
+equivalent to:
+
+ split(' ', q/STRING/);
+
+the difference being that it generates a real list at compile time. So
+this expression:
+
+ qw(foo bar baz)
+
+is semantically equivalent to the list:
+
+ 'foo', 'bar', 'baz'
+
+Some frequently seen examples:
+
+ use POSIX qw( setlocale localeconv )
+ @EXPORT = qw( foo bar baz );
+
+A common mistake is to try to separate the words with comma or to
+put comments into a multi-line C<qw>-string. For this reason, the
+C<use warnings> pragma and the B<-w> switch (that is, the C<$^W> variable)
+produces warnings if the STRING contains the "," or the "#" character.
+
=item s/PATTERN/REPLACEMENT/egimosx
Searches a string for a pattern, and if found, replaces that pattern