diff options
| author | Abigail <abigail@abigail.be> | 2012-03-23 14:15:42 +0100 |
|---|---|---|
| committer | Abigail <abigail@abigail.be> | 2012-03-23 14:15:42 +0100 |
| commit | 3258103348843907aaaabd5ce638d44c6ab5ecfa (patch) | |
| tree | 532ed6fbfdbb9017923a8a2e8bcec105ac9a986f /pod | |
| parent | 7476a79c8db21237e6b6bcf579243fdfc880f8b9 (diff) | |
| download | perl-3258103348843907aaaabd5ce638d44c6ab5ecfa.tar.gz | |
Clearify string parsing.abigail/for-5.17
It was already documented that when scanning for the end of the string,
backslashes escaping the closing delimiter are being eliminated; but
this is true for backslashes escaping backslashes as well. This makes
that C<< '.\.' eq '.\\.' >>. (Pointed out by Mithaldu)
Diffstat (limited to 'pod')
| -rw-r--r-- | pod/perlop.pod | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/pod/perlop.pod b/pod/perlop.pod index 1cb186a7a7..2152f13a5b 100644 --- a/pod/perlop.pod +++ b/pod/perlop.pod @@ -2544,8 +2544,9 @@ for closing C<]> paired with the opening C<[>, combinations of C<\\>, C<\]>, and C<\[> are all skipped, and nested C<[> and C<]> are skipped as well. However, when backslashes are used as the delimiters (like C<qq\\> and C<tr\\\>), nothing is skipped. -During the search for the end, backslashes that escape delimiters -are removed (exactly speaking, they are not copied to the safe location). +During the search for the end, backslashes that escape delimiters or +backslashes are removed (exactly speaking, they are not copied to the +safe location). For constructs with three-part delimiters (C<s///>, C<y///>, and C<tr///>), the search is repeated once more. |