Forum: Ruby Re: Q about the FasterCSV

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
6087a044557d6b59ab52e7dd20f94da8?d=identicon&s=25 Peña, Botp (Guest)
on 2006-04-28 04:39
(Received via mailing list)
Dave Burt [mailto:dave@burt.id.au] :
  James Edward Gray II wrote:
# > Good points all around.  Dave knows this code better than I do,
# > clearly.  ;)
#
# Thanks, but credit to you -- IIRC part of your stated aim for
# FasterCSV
# was to make it short, legible, and therefore maintainable,
# and if I can
# pick up this stuff in literally one minute of looking at the code,
# you've succeeded. Well done.

Dave and James, you've done a great work on csv parsing. I really do not
mind if you provide a second/another version of fastercsv.  maybe name
it fastercsv2 or lenientcsv, i do not care, as long as it does the job.
in this case, speed comes last (and ignored) once a problem is solved.

thanks for csv and kind regards -botp
4299e35bacef054df40583da2d51edea?d=identicon&s=25 James Gray (bbazzarrakk)
on 2006-04-28 06:06
(Received via mailing list)
On Apr 27, 2006, at 9:36 PM, Peña, Botp wrote:

> in this case, speed comes last (and ignored) once a problem is solved.

To me, the problem is solved.  For the record, that problem was that
the standard CSV library was too slow for some uses.  We fixed that
and more.

I'll leave the other library for you.  ;)

James Edward Gray II
This topic is locked and can not be replied to.