From: Jeff Garland (jeff_at_[hidden])
Date: 2007-01-12 01:50:58
Jody Hagins wrote:
> On Thu, 11 Jan 2007 08:22:14 -0700
> Jeff Garland <jeff_at_[hidden]> wrote:
>> Yep, all true. But until the switch in US rules there has been
>> basically zero demand for this feature. My perception is that the
>> majority usage of tz conversion usage is to convert the current time
>> or times in the near future to a local time.
> Unless you use historic log files, and the date/time is stored in basic
> format, then converted to local time. In that case, it should convert
> based on the rules in effect relative to the UT value. This is a very
> common use case, especially for simulations.
> I understand this is "new" but it seems like a candidate for fixing ASAP
> so it can go out with the 1.34 release... assuming 1.34 makes it out the
> door before the timezone change...
There's no way the 'historic tz feature' will be in 1.34 -- it's too big a
change and it's too late in the 1.34 cycle. Not to mention that I can't
really make time to work on it at the moment.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk