Hassan Schroeder wrote: [...] > Gah. I give up. That's like saying you can't discuss the abstract idea > of "pancakes" without specifying the meal they will be (or were) eaten > at.
Not quite. I can discuss the abstract idea of pancakes without mentioning ingredients, but if I want to make some for breakfast, I have to decide which type of flour to use. > > Sorry you can't visualize the use case of an *abstract* time of day. I hope that wasn't intended to be as condescending as it came out. I do understand that it might be useful to do @hassan.set_alarm_clock(AbstractTime.new(:hour => 7, :minute => 0)) But (assuming for the sake of argument that my Web server can somehow ring your alarm clock), I can hardly expect to ring your alarm clock at an abstract time. I'd need to do something like @hassan.ring_alarm(@hassan.alarm_time.concretize(:zone => @hassan.current_time_zone)) I just don't see an abstract time as being a terribly useful object, except as an argument for a concrete time constructor. > > But whatever. "Whatever"?!? I'm trying to have a serious discussion here. I thought you were too; was I mistaken? > -- > Hassan Schroeder Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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 [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 -~----------~----~----~----~------~----~------~--~---
