> Use Text::xSV instead. update And I'd agree that if a pure perl solution is needed, it is the best and should be used instead of Text::CSV.
Text::xSV is a very good moudle.
> It's pureperl, very fast,
But not as fast as Text::CSV_XS, see Benchmark comparison of Text::xSV and Text::CSV_XS. In many cases that speed difference wouldn't matter but the OP is specifically talking about large files where speed is an issue.
> and handles edge cases better than Text::CSV
Perhaps.
> or Text::CSV_XS.
Which edge cases does it handle better? See Comparison of the parsing features of CSV (and xSV) modules
> Oh - and it allows for any single-character separator. :-)
As do both Text::CSV and Text::CSV_XS.

In reply to Re^2: Text::CSV and very large Text Files by jZed
in thread Text::CSV and very large Text Files by webchalkboard

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.