Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Try to explain qw vs. Qw
  • Loading branch information
moritz committed Apr 21, 2014
1 parent 1c6b3b0 commit a807255
Showing 1 changed file with 7 additions and 2 deletions.
9 changes: 7 additions & 2 deletions lib/terms.pod
Expand Up @@ -135,7 +135,7 @@ The other quote forms add on to this basic functionality:
'(Just kidding. There\'s no money in that string)'
'No $interpolation {here}!'
The C<:q> form allows for escaping characters that would otherwise end
The C<q> form allows for escaping characters that would otherwise end
the string using a backslash. The backslash itself can be escaped, too,
as in the third example above. The usual form is C<'…'> or C<q> followed
by a delimiter, but it's also available as an adverb on C<Q>, as in the
Expand All @@ -151,7 +151,12 @@ TODO
qw|! @ # $ % ^ & * \| < > | eqv '! @ # $ % ^ & | < >'.words
Q:w { [ ] \{ \} } eqv ('[', ']', '{', '}')
The C<:w> form, usually written C«<…>» or C<qw>
The C<:w> form, usually written C«<…>» or C<qw>. It splits up the string into
words (which are, in this context, defined by sequences of non-whitespace
characters separated by whitespace). C<q:w> and C<qw> forms inherit the
interpolation and escape semantics of the C<q> and single quote string
delimiters, C<Qw> and C<Q:w> inherit the non-escaping semantis of the C<Q>
quoter.
=head3 Shell quoting: qqw
Expand Down

0 comments on commit a807255

Please sign in to comment.