-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.8 - support 1-minute resolution for all Extended timezones and most Basic timezones #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…Code; WorldClock flash actually goes down 20 bytes (#18)
…sic:: and extended::, prep for different implementations (#18)
…coded offsetCode and deltaCode; matches Hinnant date from 1972 to 2050 (#18)
…ghres encoding that supports 1-minute resolution (#18)
…d/ database, all timezones, year [1975, 2050), 1-minute resolution (#18)
…ing ExtendedZoneProcessor (#18)
…d during refactoring
… finds all 'zonedb*' subdirectories
…r, 3 lines instead of 11-12
…y in Makefiles; use --scope to autoselect --at_until_granularity and --offset_granularity
… print the debugging BasicZoneProcessor.log()
…areRulesBeforeYear()
…int8_t) instead of year (int16_t), simpler and saves 60 bytes for WorldClock
…ay, reducing special cases; add Transition.month to represent fixed ZoneEra; saves 140 bytes for WorldClock
…ds and add unit tests
…n for year+1 if the ZoneEra changes
…a is different before adding latest prior transition; matches Hinnant date and pytz from 1975-2050
…y-1); saves 76 bytes in WorldClock
…earTiny; saves 28 bytes in WorldClock
… and HardwareTemperature has no hardware dependency
…creases by 14 bytes, ExtendedZoneProcessor by 20 bytes due to higher 1-minute resolution
…numbers for 1-minute resolution (decreases memory by 80-200, prob due to changing to yearTiny calculations
…stly) of the zoneinfo files
…ast best release before 1.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fri<=1
correctly in various python scripts. (correctly handle Fri<=1 expressions in TZ database #17)resolutions for the AT and UNTIL fields.
for both STDOFF and DST offset fields.
resolution for STDOFF field and 15-minute resolution for DST offset
(with a range of -01:00 to 02:45). (4 bits of the
deltaCode
field were given to the
offsetCode
field to give it the1-minute resolution.)
2000. Did not handle transitions from fixed ZoneEra (RULES='-') to named
ZoneEra (RULES=reference) or vise versa. Verified against pytz and
Hinnant date from 1975 to 2050.