On Mon, 13 Jan 2003, fglock wrote: > > You'd think 19700329T033000. And you'd be right most of the time, > > but not if that time was a Europe/Amsterdam time. Then, it'd > > be 19700329T043000. > > > > So, I think we need to either put all of this inside the base object, > > or make the base object do UTC only. > > What if Date::Set supported add()? (which it already does, with another > name) > > I think it would be more productive to teach Date::Set a few new simple > tricks (Datetime, or Time::Piece API, whatever) than starting from a > 'dumb' base module.
If you can show me a good API for this, I'll believe it. But my gut feeling is that the API will be simpler if we can separate the nitty gritty details of timezones into their own module. > About "Rata Die" and "Julian Day": I'd prefer a seconds-based > implementation, because leap seconds would make 'seconds' be a > varying fraction, in a day-based calendar. I'm going to start a separate thread about leap seconds. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
