From 3258103348843907aaaabd5ce638d44c6ab5ecfa Mon Sep 17 00:00:00 2001 From: Abigail Date: Fri, 23 Mar 2012 14:15:42 +0100 Subject: Clearify string parsing. 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) --- pod/perlop.pod | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'pod') 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 and C), 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, C, and C), the search is repeated once more. -- cgit v1.2.1