in reply to Re^2: Escaping multiple escape chars
in thread Escaping multiple escape chars

Why would ' vs " make a difference? \\ is used as an escape character for both.

In single quote string literals, "\\" is interpreted as "\", "\'" is interpreted as "'", and everything else is left as is.

In double quoted string literals, "\\" is interpreted as "\", "\"" is interpreted as """, ...

Is there a way to make perl think the data came from a stream?

No. That makes no sense. The script doesn't know whether the data came from a stream or not. The conversion happens during the parsing of the script by the Perl parser. If it didn't do this, you would have no way of specifying certain strings, such as the one containing solely \.

Replies are listed 'Best First'.
Re^4: Escaping multiple escape chars
by JamesNC (Chaplain) on Dec 10, 2005 at 06:56 UTC
    Perhaps this example helps better what I am trying to say that context matters ( ' vs " ): 
    use Devel::Peek;

my $txt = 'some\text';

print $txt;  #prints some\text
Dump($txt);

    [download]
    versus: 
    use Devel::Peek;

my $txt = "some\text";

print $txt; #prints some [tab] ext
Dump($txt);

    [download]

    If what you were saying was true, then the first line should print the same as the second.
    The substitution: 
    use Devel::Peek;

my $txt = '\|/';
$txt =~s/\\/\\\\/g;

print $txt;
Dump($txt);

    [download]
    Produces the exact same results as: 
    use Devel::Peek;

my $txt = '\\|/';
$txt =~s/\\/\\\\/g;

print $txt;
Dump($txt);

    [download]
    Aren't they different literals? Change the ' to " and try the same test.
    I think the logic is broken here. A literal should mean, I am to be taken literally, not, interpret part of me as a literal and part of me however you take a guess, because that is what is happening or else it would store 'some\text' the same as "some\text". The parser is just getting this case incorrect I think.
[reply]
[d/l]
[select]
      ' and " are different. All of this is documented.
      A literal should mean, I am to be taken literally

      Nonsense. Literals are always interpreted. The literal 1234 in the expression $a = 1234; is a group of characters, yet they are interpreted as a number. And somehome, the quotes in the literal "abc" are removed.

      Without interpretation, the compiler wouldn't know where the string ends and/or wouldn't allow certain characters to be part of the string. For example, what if there was a quote in your ASCII art? How would Perl know the string doesn't end at that quote, but rather the following one? (or the one after that?) For single quoted strings, you preceed the quote with a backslash. Of course, now we need a method of allowing backslashes followed by single quotes...

      Whenever something is embedded in something else, be it a string in a Perl source file, a object in a data file or text between HTML tags, some form of encoding or escaping is required. To be crystal clear: You can't have strings and Perl code in the same file without some form of escaping or encoding.

[reply]
[d/l]
[select]
        I have attempted to explain my question with 2 examples using 'some\text' and "some\text" both of which get stored as I understood they should. However, 'some\\text' and "some\\text" don't behave as you would expect and are NOT stored with the same rules as the first case because in the first case, the compiler sees the single quotes and stores the characters correctly by pushing an additional '\' to the PV array as it should. What is going wrong, however, is the case when it sees a second '\' in the literal case, and doesn't push another '\' onto the PV.
        use Devel::Peek;

# literal case - PV's are the same
$txt = 'some\text';
print "Case 1 'some\\text': $txt\n-------\n";
# PV gets an extra '\' pushed on it.
Dump($txt);

$txt = 'some\\text';
print "\nCase 2 'some\\\\text: $txt\n-------\n";
#PV does NOT get an extra '\' pushed on to it
Dump($txt);

# quoted case - PV's handle '\' as expected
$txt = "some\text";
print "\nCase 3 \"some\\text\": $txt\n-------\n";
Dump($txt);

#
$txt = "some\\text";
print "\nCase 4 \"some\\\\text\": $txt\n-------\n";

Dump($txt);

        [download]
        If you actually try these examples, then you can see for yourself how the scalars are getting stored.

        Nuff said. I will ask the perl porters from here.
[reply]
[d/l]

In Section Seekers of Perl Wisdom