When parsing CSV with Text::CSV_XS or Text::CSV don't specify the eol attribute at all, and getline () most likely will do-the-right-thing.
open my $fh, "<", $file or die "$file: $!"; # Don't use auto_diag on older Text::CSV_XS my $csv_in = Text::CSV_XS->new ({ binary => 1, auto_diag => 1 }); my $csv_out = Text::CSV_XS->new ({ binary => 1, sep_char => "\t", eol + => $/ }); while (my $row = $csv->getline ($fh)) { $csv_out->print (*STDOUT, [ @{$row}[2, 3, 0, 4] ]); } $csv->eof () or $csv->error_diag (); # Not needed with auto_diag close $fh;
update: filled in the correct output syntax for a array-ref-slice
Important update: I was wrong. A single \r is not a valid line ending in the default configuration according to the CSV specs. In that case you'd have to specify that with eol => "\r". I will see if I can make it legal if the system $/ already is a "\r".
In reply to Re: line ending problem Text::CSV alternative Text::ParseWords?
by Tux
in thread line ending problem Text::CSV alternative Text::ParseWords?
by GertMT
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |