-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi James,

James Edward Gray II wrote:
>> Please do not waste your time any more. (sorry for writing this.  I know
>> you are taking much time to support users for using CSV in Ruby).
>>  Cracks are from difference of our CSV standpoints so it must not be
>> 100% compatible.
> 
> Do we have different standpoints?  I hope not too different.  We're just
> using different parsing techniques, right?

As you wrote in your document, followings are from standpoint I think.
 * streaming
 * record terminator handling

I don't think faster_csv is wrong.  I just wrote csv.rb from (a little)
different viewpoint 6 years ago.

> Other than to_csv() and parse_csv(), are there things you don't like
> about FasterCSV?  I'm open to suggestions.

No.  That's all for now.  (Sorry, I've not yet look into new CSV features)

>> Just replace csv.rb with faster_csv.rb.
> 
> I just don't want to break a lot of software.  :(

I understand that it's a compensation of speed.

>> As a bundled library (in my opiniion):
>>
>>   One thing I don't like faster_csv.rb is String#parse_csv and
>>   Array#to_csv.  Please do not bring pollution to standard classes.
>>
>>   Kernel.CSV should be discussed well before introducing it.  Needed?
>>   (We already have Kernel.URI though...)
> 
> Maybe I'm alone in this thinking, but I'm not bothered by conversion
> methods like this.  It's also fairly common (to_set(), to_yaml(), etc.).

I don't like those, too.  We should wait selector namespace. (IMO)

Regards,
// NaHi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)

iD8DBQFEeQYEf6b33ts2dPkRAjzUAKC0EAhNXkk+IiAutrWOlhWqctdXvQCgohio
BP16cwL6jGN3vnwUGj9k3sQ=
=Prwb
-----END PGP SIGNATURE-----