From: James Edward Gray II <james@...>
Date: 2007-08-08T05:08:43+09:00
Subject: Is this really what we want?

I'm investigating some recent breakage in FasterCSV and have tracking  
it down to a change in the Date standard library.  Is this really the  
desired behavior now:

   $ ruby -r date -e 'p Date.parse("junk")'
   #<Date: 4908505/2,0,2299161>

?

In previous versions of Ruby that code raised an ArgumentError, which  
I feel was a lot more correct.

In any case, if the above is now intended, the documentation for  
Date::parse is now wrong and needs to be updated.

James Edward Gray II