RFC: deprecate *_rd_as_seconds
RFC: deprecate DateTime.pm *_rd_as_seconds utc_rd_as_seconds - used internally. DateTime::TimeZone should calculate this value from utc_rd_values(), for compatibility with other calendars. - does not use nanoseconds or leap seconds local_rd_as_seconds - it looks like it was never used - does not use nanoseconds or leap seconds - Flavio S. Glock
Re: RFC: deprecate *_rd_as_seconds
On Mon, 20 Oct 2003, Flavio S. Glock wrote: > RFC: deprecate DateTime.pm *_rd_as_seconds > > utc_rd_as_seconds > > - used internally. DateTime::TimeZone should calculate this value from > utc_rd_values(), for compatibility with other calendars. > - does not use nanoseconds or leap seconds Not using nanoseconds or leap seconds is quite intentional. Since the calculated values that DT::TZ uses also don't use leap second, it works out fine. > local_rd_as_seconds > > - it looks like it was never used > - does not use nanoseconds or leap seconds Is that still in there? Wow. Yeah, that can go. -dave /*=== House Absolute Consulting www.houseabsolute.com ===*/
Re: RFC: deprecate *_rd_as_seconds
Dave Rolsky wrote: > Not using nanoseconds or leap seconds is quite intentional. Since the > calculated values that DT::TZ uses also don't use leap second, it works > out fine. Yeah, but: > On Mon, 20 Oct 2003, Flavio S. Glock wrote: > > DateTime::TimeZone should calculate this value from > > utc_rd_values(), for compatibility with other calendars. utc_rd_values() is _the_ communication method between modules. DT::TZ should use it. - Flavio S. Glock