[tz] please do not enforce limits in code for time zones

Howard Hinnant howard.hinnant at gmail.com
Mon Jan 22 19:53:56 UTC 2018

On Jan 22, 2018, at 2:44 PM, Lester Caine <lester at lsces.co.uk> wrote:
> On 22/01/18 19:22, Howard Hinnant wrote:
>> There’s a proposal before the C++ standardization committee:
>>     https://wg21.link/p0355
>> <Disclaimer> I’m the author. </Disclaimer>
> Still no means of identifying if a change of version of TZ data results in a change to a local time? At the end of the day which ever software is being used, if I provide a UTC normalised time then it also needs to identify the rule set used to create it. If different software uses different ways of storing the rules it is somewhat irrelevant as long as they all produce the same local time so any improvements to the rules should include version information. Something that has been missing for too long now.

    #include "date/tz.h"
    #include <iostream>

        std::cout << date::get_tzdb().version << '\n';





-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://mm.icann.org/pipermail/tz/attachments/20180122/b227af55/signature.asc>

More information about the tz mailing list