| Subject: | TimeZone abbreviation are ambigious |
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/