Click here to get back home

ANNOUNCE: Text-CSV_XS 0.28

 HomeNewsGroups | Search | About
 comp.lang.perl.modules    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
ANNOUNCE: Text-CSV_XS 0.28 H.Merijn Brand 06-04-2007
Posted by H.Merijn Brand on June 4, 2007, 6:54 am
Please log in for more thread options


Note the IMPORTANT CHANGE!

file: $CPAN/authors/id/H/HM/HMBRAND/Text-CSV_XS-0.28.tar.gz
size: 33289 bytes
md5: 8c00161d04793deaf383b4331fe09db4


* IMPORTANT CHANGE: new () returns undef if it gets unsupported=

attributes. Until now, new ({ esc_char =3D> "\" }) was just
silently ignored. Rejecting it and failing is better than
continuing with false assumptions.
* Added allow_loose_quotes (see doc)
* Added t/65_allow.t
* Added allow_loose_escapes (see doc) RT 15076
* More code cleanup in XS
* Added allow_whitespace (see doc)


* checked with perlcritic (still works under 5.00504)
so 3-arg open cannot be used (except in the docs)
* 3-arg open in docs too
* Added a lot to the TODO list
* Some more info on using escape character (jZed)
* Mention Text::CSV_PP in README
* Added t/45_eol.t, eol tests
* Added a section about embedded newlines in the pod
* Allow \r as eol ($/) for parsing
* More docs for eol
* More eol =3D \r fixes, tfrayner's test case added to t/45_eol=
.t


=3Ditem allow_whitespace

When this option is set to true, whitespace (TAB's and SPACE's)
surrounding the separation character is removed when parsing. So
lines like:

1 , "foo" , bar , 3 , zapp

are now correctly parsed, even though it violates the CSV specs.
Note that B<all> whitespace is stripped from start and end of each
field. That would make is more a I<feature> than a way to be able
to parse bad CSV lines, as

1, 2.0, 3, ape , monkey

will now be parsed as

("1", "2.0", "3", "ape", "monkey")

even if the original line was perfectly sane CSV.

=3Ditem allow_loose_quotes

By default, parsing fields that have C<quote_char> characters inside
an unquoted field, like

1,foo "bar" baz,42

would result in a parse error. Though it is still bad practice to
allow this format, we cannot help there are some vendors that make
their applications spit out lines styled like this.

Similar ThreadsPosted
ANNOUNCE: PDL-2.4.3 August 22, 2006, 7:46 am
[ANNOUNCE] MultiProcFactory 0.01 September 20, 2004, 6:29 am
ANNOUNCE: WWW::Webrobot 0.50 September 29, 2004, 10:46 am
ANNOUNCE: WWW::Webrobot 0.51 October 1, 2004, 9:54 am
ANNOUNCE: tclperl-3.1 October 11, 2004, 4:56 am
[ANNOUNCE] Net::FTPSSL 0.03 September 5, 2005, 4:54 pm
[ANNOUNCE] POD2::IT 0.09 September 8, 2005, 11:06 am
ANNOUNCE: Teradata::SQL v0.01 November 17, 2005, 3:23 pm
[ANNOUNCE] POD2::IT 0.10 November 21, 2005, 9:44 am
[ANNOUNCE] wxPerl 0.26 November 23, 2005, 9:41 pm

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap