I finally was able to strike the EBCDIC TODO-item. After Karl and I got perl-5.32.0 built on z/OS EBCDIC native with dynamic loading and threads, the next step was to get Text::CSV_XS passing all tests on it. We need a goal, and this one was a real challenge, but it now works, out of the box! (I updated the TODO list in the OP)
I just released 1.44, which was also tested with the new (not set in stone) defaults that the core development team envisions for perl-7, and everything passes \o/
Check out the updated tools: csv-check and csv2xlsx.
1.44 - 2020-07-22
- EBCDIC now fully functional
- Prevent false negative CPANTESTERS fail reports
- Fully tested on perl-5.32.0 and perl-5.33.0
- Fix partly decoded fields in header (found by Eric Brine)
1.43 - 2020-05-27
- Add --parser-opt=value to csv-check
- Add -L & -X to csv-check
- Fix undef value in attribute setters for strings (issue 24)
- Document quote (undef) is not supported
1.42 - 2020-05-19
- Update to Devel::PPPort-3.58
- Unicode fixes for csv2xls and csv2xlsx
- Add internal buffers to cache diagnostics
- Fix positional reporting in examples/csv-check
- Allow passing CSV parsing attributes to csv-check
- Proof reading - doc fixes by Klaus Baldermann <soonix> (PR#21)
- Fix type caching (RT#132344)
- Small doc fix by Nick Tonkin <1nickt> (PR#22)
- Fix sep=; being ignored in ->header (issue 23)
1.41 - 2020-02-16
- Update to Devel::PPPort-3.56
- csv2xls uses sheetname as csv2xlsx
- csv2xlsx: support images (each image gets its own tab)
- More docs. (Data validation)
- No binary literals in fixed error messages
- Fix auto_diag > 2 to die when headers are used (issue 19)
Enjoy, Have FUN! H.Merijn
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
