I didn't choose the name, but I agree. I'm certainly not going to do away with Text::CSV_XS since, as I said it has many users, is included e.g. in many linux distros, etc. so would cause unpredictable incoveniences to drop the name. But I agree that it would be great to combine the two and I've suggested as much to
Tilly previously - we've not done it out of time constraints rather than interest. If you look at
Comparison of the parsing features of CSV (and xSV) modules, you'll see that Text::CSV_XS has several parsing options that Text::xSV does not (mostly things not needed in ordinary CSV parsing but quite useful for odd legacy formats) so the two modules have other differences than the perl/C differences. I think Text::xSV::Fast might be a good idea, why don't you write it? It could simply subclass Text::CSV_XS and provide some wrappers to implement the Text::xSV interface.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.