note
Tux
<p>Small updates</p>
<p>I now understand the fuzz people make about embedded newlines. [mod://Text::CSV_XS] has always been able to deal with that (well, maybe not always, but at least for a long time already). The problem that people might have is <i>reading</i> the line in the perl script. Obviously,</p>
<code>
my $csv = Text::CSV_XS-New ({ binary => 1 });
while (<>) {
$csv->parse ($_);
my @fields = $csv->fields ();
</code>
<p>Will horribly fail, as <c><></c> will break too early.</p>
<p>The most recent [http://www.xs4all.nl/~hmbrand/Text-CSV_XS-0.27.tar.gz|snapshot] now contains a <c>t/45_eol.t</c>, that tests all possible eol combinations. Have a look to see that the way to parse CSV with embedded newlines should be done similar to:</p>
<code>
use IO::Handle;
my $csv = Text::CSV_XS->new ({ binary => 1, eol => $/ });
while (my $row = $csv->getline (*ARGV)) {
my @fields = @$row;
</code>
<p>or, if you open files yourself, like:</p>
<code>
my $csv = Text::CSV_XS->new ({ binary => 1, eol => $/ });
open my $io, "<", $file or die "$file: $!";
while (my $row = $csv->getline ($io)) {
my @fields = @$row;
</code>
<p>I'm still thinking about the best way to add this to the docs.</p>
<!-- Node text goes above. Div tags should contain sig only -->
<div class="pmsig"><div class="pmsig-200365">
<br />
Enjoy, Have FUN! H.Merijn
</div></div>
617577
617577