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".
Enjoy, Have FUN! H.Merijn
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.