Why use IO::File? Also when you read the input file, the line terminator is still there, and then you're adding another one with your join. Plus is your script running on Windows or Unix? If Unix, then the \r will be read, never gets removed, and then gets into the output.
I would handle this as follows:
open(my $in, "<", $inputfile) or die "Can't read '$inputfile': $!";
open(my $out, "<", $outputfile) or die "Can't read '$outputfile': $!";
binmode($out);
while (my $line = <$in>) {
$line =~ s/\r\n?/\n/g;
print $out $line;
}
close($in) or die "Can't close '$inputfile': $!";
close($out) or die "Can't close '$outputfile': $!";
This code should work on both Unix and Windows.
I actually leave out the closes usually. Putting them in will tell you if, for instance, you had a full disk. But I usually don't worry about that.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.