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 abbreviation are ambigious #10

Open
autarch opened this issue Nov 12, 2016 · 0 comments
Open

TimeZone abbreviation are ambigious #10

autarch opened this issue Nov 12, 2016 · 0 comments

Comments

@autarch
Copy link
Member

autarch commented Nov 12, 2016

Migrated from rt.cpan.org #44854 (status was 'new')

Requestors:

From [email protected] on 2009-04-07 20:27:35:

I know it says these are ambiguous in docs, but how come there isn't an
API to tell when they are ambiguous and not?

Using Moose, I can't set up a type coercion that fallsback from a failed
attempt at DateTime::TimeZone unless I know the attempt is failed.

#returns -5 which is the EST for en_US
perl -MDateTime::TimeZone -E'use XXX; say
DateTime::TimeZone->new(name=>"EST")->{spans}[0][DateTime::TimeZone::OFFSET]/60/60'

There are lots of EST's though
http://www.timeanddate.com/library/abbreviations/timezones/

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

No branches or pull requests

1 participant