Why the CSV standard library is broken (and how to fix it), Part III or Returning a CSV Record as an Array? Hash? Struct? Row?

Gerald Bauer <[email protected]>
Newsgroups gmane.comp.lang.ruby.general
Message-ID <CAAxEZd9WPV95+uknntQrO2XA31SePoqRFgoN3VLpgb=a9WGj5w@mail.gmail.com>
Hello,

  I've written a new (and third) episode [1] in the series
why the CSV standard library is broken, broken, broken (and how to fix it).

 Let's have a look at how to handle csv records. How about returning
an array? hash? struct? row? etc.

 Or how about adding new "low-level" parsers for supporting more
dialects and formats or for faster code with c-extensions?

 Questions and comments welcome. Cheers. Prost.

PS: If you want to see other (more) CSV formats / dialects pre-configured
and supported "out-of-the-box" in the new (alternative) csv reader, please tell.

PPS: Why care about CSV? Did you know - data is the new gold :-)
and CSV is the world's most popular (No. 1) data format.

[1] https://github.com/csv11/docs/blob/master/csv-array-hash-struct.md

Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.