Skip to content
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

TimeZone Bug #8

Open
seandenigris opened this issue Jan 16, 2020 · 0 comments
Open

TimeZone Bug #8

seandenigris opened this issue Jan 16, 2020 · 0 comments

Comments

@seandenigris
Copy link

Chalten seems to sidestep the terrible Pharo TZ bug for Dates, because its dates are abstract and not implemented via timestamps. However, it seems to suffer from the same bug with times, which, while at least having the ability to refer to timezones by name, still have the amorphous 'local timezone' concept. The crux of the problem is that the correct offset for a created e.g. DateTime needs to be the offset on the created date, whereas in Pharo/Chalten the offset is set to the today's offset. These can be different since the local TZ offset may vary due to DST. So if DST is in effect now, but not on the created date, the offset will be wrong. I don't see an easy way to resolve this bug and feel strongly that if timezones can't be implemented correctly, they shouldn't be enabled at all by default. See here for a fuller description of the problem.

Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant