| DateTime - A date and time object |
DateTime - A date and time object
use DateTime;
$dt = DateTime->new( year => 1964,
month => 10,
day => 16,
hour => 16,
minute => 12,
second => 47,
nanosecond => 500000000,
time_zone => 'Asia/Taipei',
);
$dt = DateTime->from_epoch( epoch => $epoch ); $dt = DateTime->now; # same as ( epoch => time() )
$year = $dt->year; $month = $dt->month; # 1-12 - also mon
$day = $dt->day; # 1-31 - also day_of_month, mday
$dow = $dt->day_of_week; # 1-7 (Monday is 1) - also dow, wday
$hour = $dt->hour; # 0-23 $minute = $dt->minute; # 0-59 - also min
$second = $dt->second; # 0-61 (leap seconds!) - also sec
$doy = $dt->day_of_year; # 1-366 (leap years) - also doy
$doq = $dt->day_of_quarter; # 1.. - also doq
$qtr = $dt->quarter; # 1-4
# all of the start-at-1 methods above have correponding start-at-0 # methods, such as $dt->day_of_month_0, $dt->month_0 and so on
$ymd = $dt->ymd; # 2002-12-06
$ymd = $dt->ymd('/'); # 2002/12/06 - also date
$mdy = $dt->mdy; # 12-06-2002
$mdy = $dt->mdy('/'); # 12/06/2002
$dmy = $dt->dmy; # 06-12-2002
$dmy = $dt->dmy('/'); # 06/12/2002
$hms = $dt->hms; # 14:02:29
$hms = $dt->hms('!'); # 14!02!29 - also time
$is_leap = $dt->is_leap_year;
# these are localizable, see Locales section $month_name = $dt->month_name; # January, February, ... $month_abbr = $dt->month_abbr; # Jan, Feb, ... $day_name = $dt->day_name; # Monday, Tuesday, ... $day_abbr = $dt->day_abbr; # Mon, Tue, ...
$epoch_time = $dt->epoch; # may return undef if the datetime is outside the range that is # representable by your OS's epoch system.
$dt2 = $dt + $duration_object;
$dt3 = $dt - $duration_object;
$duration_object = $dt - $dt2;
$dt->set( year => 1882 );
$dt->set_time_zone( 'America/Chicago' );
$dt->set_formatter( $formatter );
DateTime is a class for the representation of date/time combinations, and is part of the Perl DateTime project. For details on this project please see http://datetime.perl.org/. The DateTime site has a FAQ which may help answer many ``how do I do X?'' questions. The FAQ is at http://datetime.perl.org/.
It represents the Gregorian calendar, extended backwards in time before its creation (in 1582). This is sometimes known as the ``proleptic Gregorian calendar''. In this calendar, the first day of the calendar (the epoch), is the first day of year 1, which corresponds to the date which was (incorrectly) believed to be the birth of Jesus Christ.
The calendar represented does have a year 0, and in that way differs from how dates are often written using ``BCE/CE'' or ``BC/AD''.
For infinite datetimes, please see the DateTime::Infinite module.
The DateTime.pm module follows a simple consistent logic for determining whether or not a given number is 0-based or 1-based.
Month, day of month, day of week, and day of year are 1-based. Any
method that is 1-based also has an equivalent 0-based method ending in
``_0''. So for example, this class provides both day_of_week() and
day_of_week_0() methods.
The day_of_week_0() method still treats Monday as the first day of
the week.
All time-related numbers such as hour, minute, and second are 0-based.
Years are neither, as they can be both positive or negative, unlike any other datetime component. There is a year 0.
There is no quarter_0() method.
Some errors may cause this module to die with an error string. This
can only happen when calling constructor methods, methods that change
the object, such as set(), or methods that take parameters.
Methods that retrieve information about the object, such as year()
or epoch(), will never die.
All the object methods which return names or abbreviations return data
based on a locale. This is done by setting the locale when
constructing a DateTime object. There is also a DefaultLocale()
class method which may be used to set the default locale for all
DateTime objects created. If this is not set, then ``en_US'' is used.
Some locales may return data as Unicode. When using Perl 5.6.0 or greater, this will be a native Perl Unicode string. When using older Perls, this will be a sequence of bytes representing the Unicode character.
The default time zone for new DateTime objects, except where stated otherwise, is the ``floating'' time zone. This concept comes from the iCal standard. A floating datetime is one which is not anchored to any particular time zone. In addition, floating datetimes do not include leap seconds, since we cannot apply them without knowing the datetime's time zone.
The results of date math and comparison between a floating datetime and one with a real time zone are not really valid, because one includes leap seconds and the other does not. Similarly, the results of datetime math between two floating datetimes and two datetimes with time zones are not really comparable.
If you are planning to use any objects with a real time zone, it is strongly recommended that you do not mix these with floating datetimes.
If you are going to be using doing date math, please read the section How Datetime Math is Done.
Do not try to use named time zones (like ``America/Chicago'') with dates
very far in the future (thousands of years). The current
implementation of DateTime::TimeZone will use a huge amount of
memory calculating all the DST changes from now until the future
date. Use UTC or the floating time zone and you will be safe.
All constructors can die when invalid parameters are given.
my $dt = DateTime->new( year => 1066,
month => 10,
day => 25,
hour => 7,
minute => 15,
second => 47,
nanosecond => 500000000,
time_zone => 'America/Chicago',
);
DateTime validates the ``month'', ``day'', ``hour'', ``minute'', and ``second'', and ``nanosecond'' parameters. The valid values for these parameters are:
Invalid parameter types (like an array reference) will cause the constructor to die.
The value for seconds may be from 0 to 61, to account for leap seconds. If you give a value greater than 59, DateTime does check to see that it really matches a valid leap second.
All of the parameters are optional except for ``year''. The ``month'' and ``day'' parameters both default to 1, while the ``hour'', ``minute'', ``second'', and ``nanosecond'' parameters all default to 0.
The ``locale'' parameter should be a string matching one of the valid
locales, or a DateTime::Locale object. See the
DateTime::Locale documentation for details.
The time_zone parameter can be either a scalar or a
DateTime::TimeZone object. A string will simply be passed to the
DateTime::TimeZone->new method as its ``name'' parameter. This
string may be an Olson DB time zone name (``America/Chicago''), an
offset string (``+0630''), or the words ``floating'' or ``local''. See the
DateTime::TimeZone documentation for more details.
The default time zone is ``floating''.
The ``formatter'' can be either a scalar or an object, but the class
specified by the scalar or the object must implement a
format_datetime() method.
Because of Daylight Saving Time, it is possible to specify a local time that is ambiguous. For example, in the US in 2003, the transition from to saving to standard time occurred on October 26, at 02:00:00 local time. The local clock changed from 01:59:59 (saving time) to 01:00:00 (standard time). This means that the hour from 01:00:00 through 01:59:59 actually occurs twice, though the UTC time continues to move forward.
If you specify an ambiguous time, then the latest UTC time is always used, in effect always choosing standard time. In this case, you can simply subtract an hour to the object in order to move to saving time, for example:
# This object represent 01:30:00 standard time
my $dt = DateTime->new( year => 2003,
month => 10,
day => 26,
hour => 1,
minute => 30,
second => 0,
time_zone => 'America/Chicago',
);
print $dt->hms; # prints 01:30:00
# Now the object represent 01:30:00 saving time $dt->subtract( hours => 1 );
print $dt->hms; # still prints 01:30:00
Alternately, you could create the object with the UTC time zone, and
then call the set_time_zone() method to change the time zone. This
is a good way to ensure that the time is not ambiguous.
Another problem introduced by Daylight Saving Time is that certain local times just do not exist. For example, in the US in 2003, the transition from standard to saving time occurred on April 6, at the change to 2:00:00 local time. The local clock changes from 01:59:59 (standard time) to 03:00:00 (saving time). This means that there is no 02:00:00 through 02:59:59 on April 6!
Attempting to create an invalid time currently causes a fatal error. This may change in future version of this module.
new()
method, it accepts ``time_zone'', ``locale'', and ``formatter'' parameters.
If the epoch value is not an integer, the part after the decimal will
be converted to nanoseconds. This is done in order to be compatible
with Time::HiRes. If the floating portion extends past 9 decimal
places, it will be truncated to nine, so that 1.1234567891 will become
1 second and 123,456,789 nanoseconds.
By default, the returned object will be in the UTC time zone.
from_epoch() with the
value returned from Perl's time() function. Just as with the
new() method, it accepts ``time_zone'' and ``locale'' parameters.
By default, the returned object will be in the UTC time zone.
DateTime->now->truncate( to => 'day' );
utc_rd_values() method. All
DateTime::Calendar modules must implement this method in order to
provide cross-calendar compatibility. This method accepts a
``locale'' and ``formatter'' parameter
If the object passed to this method has a time_zone() method, that
is used to set the time zone of the newly created DateTime.pm
object.
Otherwise, the returned object will be in the floating time zone.
new() method, except for ``day''. Additionally, both ``year'' and
``month'' are required.
new() method, except that it does not accept a ``month'' or ``day''
argument. Instead, it requires both ``year'' and ``day_of_year''. The
day of year must be between 1 and 366, and 366 is only allowed for
leap years.
This class has many methods for retrieving information about an object.
ce_year(), so that
year 1 is ``1BC'' and year 0 is ``1AD''.
year_with_era(), but uses the christian_era() to get the era
name.
year_with_era(), but uses the secular_era() method to get the
era name.
By default, the values are separated by a dash (-), but this can be overridden by passing a value to the method.
The values 60 and 61 are used for leap seconds.
Half a second is 500 milliseconds.
Half a second is 500_000 microseconds. This value will be rounded to an integer.
Half a second is 500_000_000 nanoseconds.
$dt->ymd('-') . 'T' . $dt->hms(':')
($week_year, $week_number) = $dt->week;
Returns information about the calendar week which contains this datetime object. The values returned by this method are also available separately through the week_year and week_number methods.
The first week of the year is defined by ISO as the one which contains the fourth day of January, which is equivalent to saying that it's the first week to overlap the new year by at least four days.
Typically the week year will be the same as the year that the object is in, but dates at the very beginning of a calendar year often end up in the last week of the prior year, and similarly, the final few days of the year may be placed in the first week of the next year.
DateTime::TimeZone object for the datetime object.
$dt->time_zone->name. It's provided so
that one can use ``%{time_zone_long_name}'' as a strftime format
specifier.
strftime()
method in C. However, if given multiple format strings, then it will
return multiple scalars, one for each format string.
See the strftime Specifiers section for a list of all possible format specifiers.
If you give a format specifier that doesn't exist, then it is simply treated as text.
Time::Local, which uses the Unix epoch even on
machines with a different epoch (such as MacOS). Datetimes before the
start of the epoch will be returned as a negative number.
This return value from this method is always an integer.
Since the epoch does not account for leap seconds, the epoch time for 1972-12-31T23:59:60 (UTC) is exactly the same as that for 1973-01-01T00:00:00.
Epoch times cannot represent many dates on most platforms, and this method may simply return undef in some cases.
Using your system's epoch time may be error-prone, since epoch times have such a limited range on 32-bit machines. Additionally, the fact that different operating systems have different epoch beginnings is another source of possible bugs.
Time::HiRes
module.
DateTime::Event::Recurrence.
The remaining methods provided by DateTime.pm, except where otherwise
specified, return the object itself, thus making method chaining
possible. For example:
my $dt = DateTime->now->set_time_zone( 'Australia/Sydney' );
my $first = DateTime
->last_day_of_month( year => 2003, month => 3 )
->add( days => 1 )
->subtract( seconds => 1 );
new() method except for ``time_zone''. Time zones may be set using
the set_time_zone() method.
This method performs parameters validation just as is done in the
new() method.
set_locale()set() with a single key. They all
take a single parameter.
If ``week'' is given, then the datetime is set to the beginning of the week in which it occurs, and the time components are all set to 0.
DateTime::TimeZone->new().
If the new time zone's offset is different from the old time zone,
then the local time is adjusted accordingly.
For example:
my $dt = DateTime->new( year => 2000, month => 5, day => 10,
hour => 15, minute => 15,
time_zone => 'America/Los_Angeles', );
print $dt->hour; # prints 15
$dt->set_time_zone( 'America/Chicago' );
print $dt->hour; # prints 17
If the old time zone was a floating time zone, then no adjustments to the local time are made, except to account for leap seconds. If the new time zone is floating, then the UTC time is adjusted in order to leave the local time untouched.
Fans of Tsai Ming-Liang's films will be happy to know that this does work:
my $dt = DateTime->now( time_zone => 'Asia/Taipei' );
$dt->set_time_zone( 'Europe/Paris' );
Yes, now we can know ``ni3 na4 bian1 ji2dian3?''
Like the set methods, math related methods always return the object itself, to allow for chaining:
$dt->add( days => 1 )->subtract( seconds => 1 );
DateTime::Duration to the current datetime. See
the DateTime::Duration docs for more details.
add_duration() method. It
simply creates a new DateTime::Duration object using the parameters
given, and then calls the add_duration() method.
DateTime::Duration object, this method simply calls
invert() on that object and passes that new duration to the
add_duration method.
add(), this is syntactic sugar for the subtract_duration()
method.
DateTime::Duration object representing
the difference between the two dates. The duration is relative to
the object from which $datetime is subtracted. For example:
2003-03-15 00:00:00.00000000
- 2003-02-15 00:00:00.00000000
-------------------------------
= 1 month
Note that this duration is not an absolute measure of the amount of time between the two datetimes, because the length of a month varies,, as well as due to the presence of leap seconds.
The returned duration may have deltas for months, days, minutes, seconds, and nanoseconds.
DateTime::Duration object
representing some portion of the difference between two datetimes.
The delta_md() method returns a duration which contains only the
month and day portions of the duration is represented. The
delta_days() method returns a duration which contains only days.
The delta_md and delta_days methods truncate the duration so
that any fractional portion of a day is ignored. Both of these
methods operate on the date portion of a datetime only, and so
effectively ignore the time zone.
Unlike the subtraction methods, these methods always return a positive (or zero) duration.
DateTime::Duration object representing
the difference between the two dates in seconds and nanoseconds. This
is the only way to accurately measure the absolute amount of time
between two datetimes, since units larger than a second do not
represent a fixed number of seconds.
$cmp = DateTime->compare( $dt1, $dt2 );
$cmp = DateTime->compare_ignore_floating( $dt1, $dt2 );
Compare two DateTime objects. The semantics are compatible with
Perl's sort() function; it returns -1 if $a < $b, 0 if $a == $b, 1
if $a > $b.
If one of the two DateTime objects has a floating time zone, it will first be converted to the time zone of the other object. This is what you want most of the time, but it can lead to inconsistent results when you compare a number of DateTime objects, some of which are floating, and some of which are in other time zones.
If you want to have consistent results (because you want to sort a
number of objects, for example), you can use the
compare_ignore_floating() method:
@dates = sort { DateTime->compare_ignore_floating($a, $b) } @dates;
In this case, objects with a floating time zone will be sorted as if they were UTC times.
Since DateTime objects overload comparison operators, this:
@dates = sort @dates;
is equivalent to this:
@dates = sort { DateTime->compare($a, $b) } @dates;
DateTime objects can be compared to any other calendar class that
implements the utc_rd_values() method.
It's important to have some understanding of how datetime math is
implemented in order to effectively use this module and
DateTime::Duration.
If you want to simplify your life and not have to think too hard about the nitty-gritty of datetime math, I have several recommendations:
my $dt = DateTime->now( time_zone => 'floating' );
Math done on two objects in the floating time zone produces very predictable results.
my $dt = DateTime->new( %user_input, time_zone => $user_tz );
$dt->set_time_zone('UTC');
# do various operations - store it, retrieve it, add, subtract, etc.
$dt->set_time_zone($user_tz); print $dt->datetime;
DateTime.pm are
predictable and correct, and mostly intuitive, but datetime math gets
very ugly when time zones are involved, and there are a few strange
corner cases involving subtraction of two datetimes across a DST
change.
If you can always use the floating or UTC time zones, you can skip ahead to Leap Seconds and Date Math
delta_md() or delta_days(), not
subtract_datetime(). This will give predictable, unsurprising
results, free from DST-related complications.
subtract_datetime() and add_duration()$dt2 - $dt1 = $dur $dt1 + $dur = $dt2 $dt2 - $dur = $dt1
Note that using delta_days ensures that this formula always works,
regardless of the timezone of the objects involved, as does using
subtract_datetime_absolute(). Anything may sometimes be
non-reversible.
The parts of a duration can be broken down into five parts. These are months, days, minutes, seconds, and nanoseconds. Adding one month to a date is different than adding 4 weeks or 28, 29, 30, or 31 days. Similarly, due to DST and leap seconds, adding a day can be different than adding 86,400 seconds, and adding a minute is not exactly the same as 60 seconds.
We cannot convert between these units, except for seconds and nanoseconds, because there is no fixed conversion between the two units, because of things like leap seconds, DST changes, etc.
DateTime.pm always adds (or subtracts) days, then months, minutes,
and then seconds and nanoseconds. If there are any boundary
overflows, these are normalized at each step. For the days and months
(the calendar) the local (not UTC) values are used. For minutes and
seconds, the local values are used. This generally just works.
This means that adding one month and one day to February 28, 2003 will produce the date April 1, 2003, not March 29, 2003.
my $dt = DateTime->new( year => 2003, month => 2, day => 28 );
$dt->add( months => 1, days => 1 );
# 2003-04-01 - the result
On the other hand, if we add months first, and then separately add days, we end up with March 29, 2003:
$dt->add( months => 1 )->add( days => 1 );
# 2003-03-29
We see similar strangeness when math crosses a DST boundary:
my $dt = DateTime->new( year => 2003, month => 4, day => 5,
hour => 1, minute => 58,
time_zone => "America/Chicago",
);
$dt->add( days => 1, minutes => 3 ); # 2003-04-06 02:01:00
$dt->add( minutes => 3 )->( days => 1 ); # 2003-04-06 03:01:00
Note that if you converted the datetime object to UTC first you would get predictable results.
If you want to know how many seconds a duration object represents, you have to add it to a datetime to find out, so you could do:
my $now = DateTime->now( time_zone => 'UTC' ); my $later = $now->clone->add_duration($duration);
my $seconds_dur = $later->subtract_datetime_absolute($now);
This returns a duration which only contains seconds and nanoseconds.
If we were add the duration to a different datetime object we might get a different number of seconds.
If you need to do lots of work with durations, take a look at Rick
Measham's DateTime::Format::Duration module, which lets you present
information from durations in many useful ways.
There are other subtract/delta methods in DateTime.pm to generate
different types of durations. These methods are
subtract_datetime(), subtract_datetime_absolute(),
delta_md(), delta_days(), and delta_ms().
Date subtraction is done solely based on the two object's local datetimes, with one exception to handle DST changes. Also, if the two datetime objects are in different time zones, one of them is converted to the other's time zone first before subtraction. This is best explained through examples:
The first of these probably makes the most sense:
my $dt1 = DateTime->new( year => 2003, month => 5, day => 6,
time_zone => 'America/Chicago',
);
# not DST
my $dt2 = DateTime->new( year => 2003, month => 11, day => 6,
time_zone => 'America/Chicago',
);
# is DST
my $dur = $dt2->subtract_datetime($dt1);
# 6 months
Nice and simple.
This one is a little trickier, but still fairly logical:
my $dt1 = DateTime->new( year => 2003, month => 4, day => 5,
hour => 1, minute => 58,
time_zone => "America/Chicago",
);
# is DST
my $dt2 = DateTime->new( year => 2003, month => 4, day => 7,
hour => 2, minute => 1,
time_zone => "America/Chicago",
);
# not DST
my $dur = $dt2->subtract_datetime($dt1);
# 2 days and 3 minutes
Which contradicts the result this one gives, even though they both make sense:
my $dt1 = DateTime->new( year => 2003, month => 4, day => 5,
hour => 1, minute => 58,
time_zone => "America/Chicago",
);
# is DST
my $dt2 = DateTime->new( year => 2003, month => 4, day => 6,
hour => 3, minute => 1,
time_zone => "America/Chicago",
);
# not DST
my $dur = $dt2->subtract_datetime($dt1);
# 1 day and 3 minutes
This last example illustrates the ``DST'' exception mentioned earlier. The exception accounts for the fact 2003-04-06 only lasts 23 hours.
And finally:
my $dt2 = DateTime->new( year => 2003, month => 10, day => 26,
hour => 1,
time_zone => 'America/Chicago',
);
my $dt1 = $dt2->clone->subtract( hours => 1 );
my $dur = $dt2->subtract_datetime($dt1);
# 60 minutes
This seems obvious until you realize that subtracting 60 minutes from
$dt2 in the above example still leaves the clock time at
``01:00:00''. This time we are accounting for a 25 hour day.
Date math operations are not always reversible. This is because of
the way that addition operations are ordered. As was discussed
earlier, adding 1 day and 3 minutes in one call to add() is not the
same as first adding 3 minutes and 1 day in two separate calls.
If we take a duration returned from subtract_datetime() and then
try to add or subtract that duration from one of the datetimes we just
used, we sometimes get interesting results:
my $dt1 = DateTime->new( year => 2003, month => 4, day => 5,
hour => 1, minute => 58,
time_zone => "America/Chicago",
);
my $dt2 = DateTime->new( year => 2003, month => 4, day => 6,
hour => 3, minute => 1,
time_zone => "America/Chicago",
);
my $dur = $dt2->subtract_datetime($dt1); # 1 day and 3 minutes
$dt1->add_duration($dur); # gives us $dt2
$dt2->subtract_duration($dur); # gives us 2003-04-05 02:58:00 - 1 hour later than $dt1
The subtract_dauration() operation gives us a (perhaps) unexpected
answer because it first subtracts one day to get 2003-04-05T03:01:00
and then subtracts 3 minutes to get the final result.
If we explicitly reverse the order we can get the original value of
$dt1. This can be facilitated by DateTime::Duration's
calendar_duration() and clock_duration() methods:
$dt2->subtract_duration( $dur->clock_duration )
->subtract_duration( $dur->calendar_duration );
The presence of leap seconds can cause even more anomalies in date math. For example, the following is a legal datetime:
my $dt = DateTime->new( year => 1972, month => 12, day => 31,
hour => 23, minute => 59, second => 60,
time_zone => 'UTC' );
If we do the following:
$dt->add( months => 1 );
Then the datetime is now ``1973-02-01 00:00:00'', because there is no 23:59:60 on 1973-01-31.
Leap seconds also force us to distinguish between minutes and seconds during date math. Given the following datetime:
my $dt = DateTime->new( year => 1972, month => 12, day => 31,
hour => 23, minute => 59, second => 30,
time_zone => 'UTC' );
we will get different results when adding 1 minute than we get if we add 60 seconds. This is because in this case, the last minute of the day, beginning at 23:59:00, actually contains 61 seconds.
Here are the results we get:
# 1972-12-31 23:59:30 - our starting datetime
$dt->clone->add( minutes => 1 ); # 1973-01-01 00:00:30 - one minute later
$dt->clone->add( seconds => 60 ); # 1973-01-01 00:00:29 - 60 seconds later
$dt->clone->add( seconds => 61 ); # 1973-01-01 00:00:30 - 61 seconds later
When math crosses a daylight saving boundary, a single day may have more or less than 24 hours.
For example, if you do this:
my $dt = DateTime->new( year => 2003, month => 4, day => 5,
hour => 2,
time_zone => 'America/Chicago',
);
$dt->add( days => 1 );
then you will produce an invalid local time, and therefore an exception will be thrown.
However, this works:
my $dt = DateTime->new( year => 2003, month => 4, day => 5,
hour => 2,
time_zone => 'America/Chicago',
);
$dt->add( hours => 24 );
and produces a datetime with the local time of ``03:00''.
If all this makes your head hurt, there is a simple alternative. Just convert your datetime object to the ``UTC'' time zone before doing date math on it, and switch it back to the local time zone afterwards. This avoids the possibility of having date math throw an exception, and makes sure that 1 day equals 24 hours. Of course, this may not always be desirable, so caveat user!
This module explicitly overloads the addition (+), subtraction (-), string and numeric comparison operators. This means that the following all do sensible things:
my $new_dt = $dt + $duration_obj;
my $new_dt = $dt - $duration_obj;
my $duration_obj = $dt - $new_dt;
foreach my $dt ( sort @dts ) { ... }
Additionally, the fallback parameter is set to true, so other derivable operators (+=, -=, etc.) will work properly. Do not expect increment (++) or decrement (--) to do anything useful.
If you attempt to sort DateTime objects with non-DateTime.pm objects
or scalars (strings, number, whatever) then an exception will be
thrown. Using the string comparison operators, eq or ne, to
compare a DateTime.pm always returns false.
The module also overloads stringification to use the iso8601()
method.
You can optionally specify a ``formatter'', which is usually a DateTime::Format::* object/class, to control how the stringification of the DateTime object.
Any of the constructor methods can accept a formatter argument:
my $formatter = DateTime::Format::Strptime->new(...); my $dt = DateTime->new(year => 2004, formatter => $formatter);
Or, you can set it afterwards:
$dt->set_formatter($formatter); $formatter = $dt->formatter();
Once you set the formatter, the overloaded stringification method will
use the formatter. If unspecified, the iso8601() method is used.
A formatter can be handy when you know that in your application you want to stringify your DateTime objects into a special format all the time, for example to a different language.
The following specifiers are allowed in the format string given to the
strftime() method:
%3N milliseconds (3 digits) %6N microseconds (6 digits) %9N nanoseconds (9 digits)
%{method} name
where ``method'' is a valid DateTime.pm object method.
As of version 0.13, DateTime implements Storable hooks in order to reduce the size of a serialized DateTime object.
The tests in 20infinite.t seem to fail on some machines, particularly on Win32. This appears to be related to Perl's internal handling of IEEE infinity and NaN, and seems to be highly platform/compiler/phase of moon dependent.
If you don't plan to use infinite datetimes you can probably ignore this. This will be fixed (somehow) in future versions.
Support for this module is provided via the datetime@perl.org email list. See http://datetime.perl.org/?MailingList for details.
Please submit bugs to the CPAN RT system at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=datetime or via email at bug-datetime@rt.cpan.org.
Dave Rolsky <autarch@urth.org>
However, please see the CREDITS file for more details on who I really stole all the code from.
Copyright (c) 2003-2006 David Rolsky. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
Portions of the code in this distribution are derived from other works. Please see the CREDITS file for more details.
The full text of the license can be found in the LICENSE file included with this module.
datetime@perl.org mailing list
| DateTime - A date and time object |