Why the CSV standard library is broken, broken, broken (and how to fix it), Part II or The Wonders of CSV Formats / Dialects

Hello,

   I've written a follow-up [1] on why the CSV standard library is
broken, broken, broken. Let's have a look at the wonders of CSV
formats / dialects
such as MYSQL CSV export or PostgreSQL CSV or TEXT export.

In a nutshell - the standard CSV parser is a (simplistic) kludge
using string.split() and, thus, needs to get replaced with a "real" parser
that can handle more "edge" cases / formats.

   Questions and comments welcome.

   Also if want to see other CSV formats pre-configured and supported
"out-of-the-box"  in the new csv reader, let us know.

   Cheers. Prost.


PS: Did you miss the first part (part I in the series)? See [2]

[1]: https://github.com/csv11/docs/blob/master/csv-formats.md
         (Part II - Follow-up)
[2]: https://github.com/csv11/docs/blob/master/why-the-csv-stdlib-is-broken.md
 (Part I)

Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>