However, 'some\\text' and "some\\text" don't behave as you would expect
I got the following (abbreiviated) results:
Case 1 'some\text': some\text ------- PV = 0x1aa01f0 "some\\text"\0 Case 2 'some\\text: some\text ------- PV = 0x1aa01f0 "some\\text"\0 Case 3 "some\text": some ext ------- PV = 0x1aa01f0 "some\text"\0 Case 4 "some\\text": some\text ------- PV = 0x1aa01f0 "some\\text"\0
If you obtained the above, perl behaved as expected (or at least as documented). According to to the relevant docs,
double-quoted string literals are subject to backslash and variable substitution; single-quoted strings are not (except for \' and \\).
In single quotes, perl interprets the backslash literally (instead of an escape) unless followed by another backslash or by a single quote. This DWIM most of the time, since few characters ever need to be escaped in single-quoted strings. For example, '\n' results in the string {backslash}+{lowercase n}.
In double quotes, perl interprets the backslash and the following character as an escape (instead of literally). How perl interprets an invalid/unrecognized escape sequence is undocumented (or unclearly documented), but the behaviour has consistently been to replace the escape sequence with the character that followed the backslash. This DWIM most of the time, since the extra backslash was probably a case of overzealous escaping. For example, "\<" results in the string {right angle bracket}.
If you don't see the necessity of the equivalency of
"some\\text"
and
'some\\text'
try answering the following questions:
In reply to Re^7: Escaping multiple escape chars
by ikegami
in thread Escaping multiple escape chars
by JamesNC
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |