Ruby on Rails

Greg Donald wrote:
> Not all apps require multi-timezone capabilities. Like when everyone
> is in one office, using the same calendar app.
>
> Dreaming up edge cases isn't going to make those time (without date)
> fields any less useful to those of us who use them.

You're still missing my point entirely. We're talking about representing
a time with a Time object. It matters not whether you need to support
multi-timezone or not. AFAIK there is no Ruby object that represents
time without date. The Time object represents an instant in date/time,
not some offset from midnight.

I hope that makes my meaning more clear.
--
Posted via http://www.ruby-forum.com/.

--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.