Rutger ter Borg-2 wrote:
Hey Luke,
unfortunately my work didn't lead to anything yet except for having implemented the ability to read and use the binary format of the timezone database files (both the 32 and 64 bit parts).
time_zone_base has a couple of presumptions which prevent a correct implementation of the Olson database:
1) dst_local_start_time / end_time assumes one such event per year (may be less or more in time zone transition years / countries that don't do DST). A correct interface should assume a series of zone transition points (usually two per year for a given area/location).
2) all *zone_name, *zone_abbrev functions should be a function of time, i.e., it needs a ptime parameter. The zone naming may change over time (e.g., if a country changes their time zone).
Cheers,
Rutger
Thanks, Rutger. Realistically, is a change to time_zone_base a possibility? How many people depend directly on this interface? Or could we extend the interface with the required functions without breaking existing code? Cheers, Luke -- View this message in context: http://boost.2283326.n4.nabble.com/date-time-Time-zone-improvements-tp265279... Sent from the Boost - Dev mailing list archive at Nabble.com.