On Jul 12, 4:09 am, Josh <[email protected]> wrote: > > After looking into conversions.rb. It appears that rails thinks of > time as a datetime and this doesn't seem proper, especially when Date > does not. Why should a random date be assigned to the time? > > I'll happily make a patch, but I thought to ask if there was some sort > of reasoning behind this, or a special circumstance I will destroy > when allowing to a Time hash conversion like Date has, which is > independent of datetime?
The root of the issue is that there is no pure time of day class in ruby (which is why Time is used). Maybe the right thing to do would be to write such a class (although you'd have a large backwards compatibility task). Fred > > -Josh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
