You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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'
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/
The text was updated successfully, but these errors were encountered: