I'm trying the simplest test case I could think of, but I can't get your suggestion to work. Here is what I'm trying.

#!/usr/bin/perl

use strict;
use warnings;

use Text::CSV_XS;
use Data::Dumper;
use IO::File;

my $fh = IO::File->new;
$fh->open( "<test.csv" ) or die $!;

my $c = Text::CSV_XS->new( { binary => 1, csv_eol => "\015" }  );

my $d = $c->getline( $fh );

print Dumper( $d );
[download]

And test.csv contains:

foo,bar,baz^Mred,green,blue^Mnarf,blatz,quux
[download]

(Where ^M's are \r's)

That script results in $d being undef, as reported by Data::Dumper. Running the script on the same data with \n's instead of \r's works fine.

Ooops, sorry, I was giving you DBD::CSV instructions, not Text::CSV_XS instructions, use "eol=>" instead of "csv_eol=>".

Taking a brief stroll through the Text::CSV_XS code, it looks to me like Decode() doesn't support the eol parameter. I see support in Encode() though... Check it out:

http://search.cpan.org/grep?release=Text-CSV_XS-0.23&string=eol&i=1&n=1

-sam

I'm afraid that still gives me the same result. :(