> > If you can find the trac tickets where this has been discussed and
> > perhaps when it was first introduced we could figure out what was
> > going on.
>
>
> http://dev.rubyonrails.org/ticket/2391
>
> If the answer is that this particular group of people have a binary view
> of dates, then waddya gonna do?
>
> If I can override the behavior somehow, that would be fine with me too.
> I can design around it in the future, but I would like the option if
> it's possible.
Unfortunately even if we did want to fix this, I'm not sure what the
accessors could return:
>> Date.civil(0,0,0)
ArgumentError: invalid date
from
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/date.rb:727:in
`civil'
from (irb):9
>> Date.ordinal(0,0)
ArgumentError: invalid date
from
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/date.rb:707:in
`ordinal'
from (irb):10
>>
Ruby's date libraries are having none of that.
--
Cheers
Koz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
