in reply to How do I read an entire file into a string?

I'm reading a text file on Windows. I used the first solution on this page and then print the result in $string

: 
{
  local $/ = undef;
  open FILE, "myfile" or die "Couldn't open file: $!";
  binmode FILE;
  $string = <FILE>;
  close FILE;
}
print $string;

[download]

I noticed that the "end-of-line" for each line is changed from "0d 0a" to "0d 0d 0a"

I found that if I removed the "binmode FILE;" statement, "end-of-line" for each line is correctly printed as "0d 0a": 

{
  local $/ = undef;
  open FILE, "myfile" or die "Couldn't open file: $!";
  $string = <FILE>;
  close FILE;
}
print $string;

[download]

Replies are listed 'Best First'.
Re: Answer: How do I read an entire file into a string?
by BrowserUk (Patriarch) on Jun 15, 2016 at 00:22 UTC
    I noticed that the "end-of-line" for each line is changed from "0d 0a" to "0d 0d 0a"

    Windows converts 0x0a to 0x0d 0x0a on output unless the output file handle has been marked binary (as with binmode).

    On input, it does the reverse, converting 0x0d 0x0a to 0x0a; if the file hasn't been marked binary..

    What is happening in your case is that when the text file is written, 0x0a becomes 0x0d 0x0a. When you read it in as binary, no conversion is done so you get 0x0d 0x0a in memory...

    But when you print it to the text mode screen, the automatic conversion is done (again), so 0x0d 0x0a becomes 0x0d 0x0d 0x0a as you are seeing.

    When you omit the binmode, the 0x0d 0x0a read from disk, become just 0x0a in memory; and then when you print it out, they get converted back to 0x0d 0x0a and everything looks normal.

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
    In the absence of evidence, opinion is indistinguishable from prejudice. Not understood.
[reply]
[reply]
[d/l]

        Discussion about chomp doesn't explain the binmod problem. It's related, but really quite separate.

        With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
        In the absence of evidence, opinion is indistinguishable from prejudice. Not understood.
[reply]
Re: Answer: How do I read an entire file into a string?
by Anonymous Monk on Jun 15, 2016 at 00:18 UTC
[reply]

In Section Seekers of Perl Wisdom