Skip Menu |

This queue is for tickets about the Text-CSV CPAN distribution.

Report information
The Basics
Id: 100390
Status: open
Priority: 0/
Queue: Text-CSV

People
Owner: Nobody in particular
Requestors: andrew.moise [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Seems like eol should default to newline
Date: Sun, 16 Nov 2014 18:16:52 -0500
To: bug-Text-CSV [...] rt.cpan.org
From: Andrew Moise <andrew.moise [...] gmail.com>
Hello! It seems to me that the 'eol' option for Text::CSV should default to a newline -- I don't see the advantage of defaulting to undef, because that produces unusable CSV files. It's not a tremendous problem to set 'eol', just as I say I don't see any downside (and I do see a small savings in programmer time and difficulty) to defaulting to having things work without a special option. Thanks in advance, have a good day. -Andrew
On Mon Nov 17 08:17:01 2014, andrew.moise@gmail.com wrote: Show quoted text
> Hello! > It seems to me that the 'eol' option for Text::CSV should default to > a newline -- I don't see the advantage of defaulting to undef, because > that produces unusable CSV files. It's not a tremendous problem to set > 'eol', just as I say I don't see any downside (and I do see a small > savings in programmer time and difficulty) to defaulting to having > things work without a special option. > Thanks in advance, have a good day. > -Andrew
Hi. This is because the desired eol value differs when you generate a CSV file and when you parse a CSV file. See https://metacpan.org/pod/Text::CSV_XS#eol and also https://metacpan.org/pod/Text::CSV_XS#Embedded-newlines for more details.