in reply to Re^3: Comparison of the parsing features of CSV (and xSV) modules
in thread Comparison of the parsing features of CSV (and xSV) modules

T> Which of the above user-defined features does DBD::AnyData need? All of them? Some? We probably should offline a discussion of how to provide them in a sane manner.

JZ> I'll think it over and msg you. I'm not sure it's worth your trouble if you don't have other uses for them. As I said, the minuses in the chart don't necessarily indicate a lack. Your module covers most of the formats people need, the other modules fill in the gaps for some odd formats that cover the edge cases.

T> Some are already present in some form.

JZ> I'll take a closer look and revise the chart.

T> because I got tired of bug reports about invalid csv files, by default Text::xSV will treat either \n or \r\n as a newline, so files produced on Windows can be read on Unix and vice versa.

JZ> I hear you. :-)

  • Comment on Re^4: Comparison of the parsing features of CSV (and xSV) modules