while (<FILE>) {
    s/\r?\n$//;    # If there is no \r, so what?

    # Random code
}
[download]

while ( my $line = <FILE> ) {
   chomp $line; # remove new line
   #Random code
}
[download]

to add more value to Burak's post
chomp $line; # remove new line

from chomp
This safer version of "chop" removes any trailing string that corresponds to the current value of $/ (also known as $INPUT_RECORD_SEPARATOR in the English module).

---

Vivek
-- In accordance with the prarabdha of each, the One whose function it is to ordain makes each to act. What will not happen will never happen, whatever effort one may put forth. And what will happen will not fail to happen, however much one may seek to prevent it. This is certain. The part of wisdom therefore is to stay quiet.

Ooops!! I meant to write While, rather than for each. I don't think for each in my code even works properly as it is written. I will update and make note.

On a side note, why is For Each less efficient than While? Aren't they the same in this context?

----
Thanks for your patience.

foreach will make a list out of the file's contents and then will iterate, so it will read the whole file into memory. while has a small footprint since it goes through the contents line by line plus it terminates when the the condition will evaluate to false;with foreach you go through everything in the list

Use dos2unix, flip or flip: Newline conversion between Unix, Macintosh and MS-DOS ASCII files to convert.

Or see Super Search: newline regex.

while (<$fh>) {
   # If the file contained lines ending with CRLF, $_ ends with LF
   # If the file contained lines ending with LF,   $_ ends with LF
   chomp;  # Removes LF
}
[download]

while (<$fh>) {
   # If the file contained lines ending with CRLF, $_ ends with CRLF
   # If the file contained lines ending with LF,   $_ ends with LF
   s/\r?\n\z//;  # Removes CRLF or LF
}
[download]

And since the latter works on Windows as well, you can just use it everywhere.

The only systems where this doesn't work are old Macs.

I asked a similar question in Newlines: reading files that were created on other platforms. In summary, I started with these options:

1. Use $^O, but if I understand it correctly that will just tell me about the system the program is running on, which (as exemplified here) is not necessarily the same as the system that created the file.
2. Use a regex to match the newline character(s) in the file. I think this would require slurping the whole file and then doing something like if( $file =~ m/\015$/ ) (which assumes the file will end with a newline) or if( $file =~ m/\015(?!\012)/ ) (which doesn't), setting $/ according to what matched, and re-reading the file line-by-line.
3. Preprocess the input file to convert all newline characters to the current system's newline character. I experimented a little, and I think this will work:
   

       $file =~ s[(\015)?\012(?!\015)][\n]g;
       $file =~ s[(\012)?\015(?!\012)][\n]g;
   [download]

I ended up implementing the preprocessing solution, but I would probably use binmode if I were to do it today.

    local $_ = "";
    while( sysread FH, $_, 8192, length ) {
        while( s/^((?s).*?)your_pattern/ ) {
            my $record = $1;
            # do stuff here.
        }
    }
[download]

Another hour to figure out why $_ needed to be localized

Because you change its value. Clobbering your caller's variables isn't nice.

Yes, I know the bug in this example. It's exactly how it is on the perldocs

perlbug