Class-Date
view release on metacpan or search on metacpan
README.mkdn view on Meta::CPAN
becomes "2001-03-03". This is the default behaviour.
When $MONTH\_BORDER\_ADJUST is true, this result becomes "2001-02-28". So when
the date overflows, then it returns the last day insted.
Both settings keep the time information.
# TIMEZONE SUPPORT
Since 1.0.11, Class::Date handle timezones natively on most platforms (see
the BUGS AND LIMITATIONS section for more info).
When the module is loaded, then it determines the local base timezone by
calling the Class::Date::local\_timezone() function, and stores these values
into two variables, these are: $Class::Date::LOCAL\_TIMEZONE and
$Class::Date::DEFAULT\_TIMEZONE. The first value is used, when you call the
"localdate" function, the second value is used, when you call the "date"
function and you don't specify the timezone. There is
a $Class::Date::GMT\_TIMEZONE function also, which is used by the "gmdate"
function, this is set to 'GMT'.
README.mkdn view on Meta::CPAN
```perl
http://perl.apache.org/docs/2.0/user/troubleshooting/troubleshooting.html#C_Libraries_Don_t_See_C__ENV__Entries_Set_by_Perl_Code
```
You are sure have this problem if the $Class::Date::NOTZ\_TIMEZONE variable
is set to 'UTC', althought you are sure that your timezone is not that. Try
\-EnvC in this case, but make sure that you are not using it in a
multi-threaded environment!
# OTHER BUGS AND LIMITATIONS
- Not all date/time values can be expressed in all timezones. For example:
```
print date("2010-10-03 02:00:00", "Australia/Sydney")
# it will print 2010-10-03 03:00:00
```
No matter how hard you try you, you are not going to be able to express the
time in the example in that timezone. If you don't need the timezone
lib/Class/Date.pm view on Meta::CPAN
becomes "2001-03-03". This is the default behaviour.
When $MONTH_BORDER_ADJUST is true, this result becomes "2001-02-28". So when
the date overflows, then it returns the last day insted.
Both settings keep the time information.
=head1 TIMEZONE SUPPORT
Since 1.0.11, Class::Date handle timezones natively on most platforms (see
the BUGS AND LIMITATIONS section for more info).
When the module is loaded, then it determines the local base timezone by
calling the Class::Date::local_timezone() function, and stores these values
into two variables, these are: $Class::Date::LOCAL_TIMEZONE and
$Class::Date::DEFAULT_TIMEZONE. The first value is used, when you call the
"localdate" function, the second value is used, when you call the "date"
function and you don't specify the timezone. There is
a $Class::Date::GMT_TIMEZONE function also, which is used by the "gmdate"
function, this is set to 'GMT'.
lib/Class/Date.pm view on Meta::CPAN
environment variables and mod_perl to get the idea why it is required
sometimes:
http://perl.apache.org/docs/2.0/user/troubleshooting/troubleshooting.html#C_Libraries_Don_t_See_C__ENV__Entries_Set_by_Perl_Code
You are sure have this problem if the $Class::Date::NOTZ_TIMEZONE variable
is set to 'UTC', althought you are sure that your timezone is not that. Try
-EnvC in this case, but make sure that you are not using it in a
multi-threaded environment!
=head1 OTHER BUGS AND LIMITATIONS
=over 4
=item *
Not all date/time values can be expressed in all timezones. For example:
print date("2010-10-03 02:00:00", "Australia/Sydney")
# it will print 2010-10-03 03:00:00
( run in 0.556 second using v1.01-cache-2.11-cpan-4d50c553e7e )