From: Yusuke ENDOH Date: 2010-01-31T19:40:33+09:00 Subject: [ruby-core:27982] Re: [Bug:trunk] some behavior changes of lib/csv.rb between 1.8 and 1.9 Hi, 2010/1/31 James Edward Gray II : > On Jan 28, 2010, at 11:13 AM, James Edward Gray II wrote: > >> On Jan 28, 2010, at 10:51 AM, Yusuke ENDOH wrote: >> >>> 4) CSV.parse_line >>> >>> $ ruby18 -rcsv -ve 'p CSV.parse_line ""' >>> [nil] >>> >>> $ ruby19 -rcsv -ve 'p CSV.parse_line ""' >>> nil >> >> We could probably debate this one. It may be that FasterCSV should return a [] instead of nil. I'll make a not to look into that and maybe fix it. We won't be going back to the CSV response of [nil] though, since I don't understand it. (See my answer to #3.) > > I take back what I said here. FasterCSV has the convention of returning nil to signal the end of data, as an IO object would. Thus, this change is intended and should probably not be changed (because FasterCSV would then be inconsistent with its own rules). Yessir. I have changed csv of rubyspec, though there is still no spec of CSV.parse_line. It would be helphul if you could take a look at csv of rubyspec in your spare time: http://github.com/rubyspec/rubyspec/tree/master/library/csv/ -- Yusuke ENDOH