DateTime::Format::Epoch (3pm)

  use DateTime::Format::Epoch;

  my $dt = DateTime->new( year => 1970, month => 1, day => 1 );
  my $formatter = DateTime::Format::Epoch->new(
                      epoch          => $dt,
                      unit           => 'seconds',
                      type           => 'int',    # or 'float', 'bigint'
                      skip_leap_secondss => 1,
                      start_at       => 0,
                      local_epoch    => undef,
                  );

  my $dt2 = $formatter->parse_datetime( 1051488000 );
   # 2003-04-28T00:00:00

  $formatter->format_datetime($dt2);
   # 1051488000

This module can convert a DateTime object (or any object that can be converted to a DateTime object) to the number of seconds since a given epoch. It can also do the reverse.

• new( ... ) Constructor of the formatter/parser object. It can take the following parameters: \*(L"epoch\*(R", \*(L"unit\*(R", \*(L"type\*(R", \*(L"skip_leap_seconds\*(R", \*(L"start_at\*(R", \*(L"local_epoch\*(R" and \*(L"dhms\*(R". The epoch parameter is the only required parameter. It should be a DateTime object (or at least, it has to be convertible to a DateTime object). This datetime is the starting point of the day count, and is usually numbered 0. If you want to start at a different value, you can use the start_at parameter. The unit parameter can be \*(L"seconds\*(R", \*(L"milliseconds, \*(R"microseconds\*(L" or \*(R"nanoseconds\*(L". The default is \*(R"seconds". If you need any other unit, you must specify the number of units per second. If you specify a number of units per second below 1, the unit will be longer than a second. In this way, you can count days: unit => 1/86_400. The type parameter specifies the type of the return value. It can be \*(L"int\*(R" (returns integer value), \*(L"float\*(R" (returns floating point value), or \*(L"bigint\*(R" (returns Math::BigInt value). The default is either \*(L"int\*(R" (if the unit is \*(L"seconds\*(R"), or \*(L"bigint\*(R" (if the unit is nanoseconds). The default behaviour of this module is to skip leap seconds. This is what (most versions of?) \s-1UNIX\s0 do. If you want to include leap seconds, set skip_leap_seconds to false. Some operating systems use an epoch defined in the local timezone of the computer. If you want to use such an epoch in this module, you have two options. The first is to submit a DateTime object with the appropriate timezone. The second option is to set the local_epoch parameter to a true value. In this case, you should submit an epoch with a floating timezone. The exact epoch used in \*(C`format_datetime\*(C' will then depend on the timezone of the object you pass to \*(C`format_datetime\*(C'. Most often, the time since an epoch is given in seconds. In some circumstances however it is expressed as a number of days, hours, minutes and seconds. This is done by \s-1NASA\s0, for the so called Mission Elapsed Time. For example, 2/03:45:18 \s-1MET\s0 means it has been 2 days, 3 hours, 45 minutes, and 18 seconds since liftoff. If you set the dhms parameter to true, format_datetime returns a four element list, containing the number of days, hours, minutes and seconds, and parse_datetime accepts the same four element list.

• format_datetime($datetime) Given a DateTime object, this method returns the number of seconds since the epoch.

• parse_datetime($secs) Given a number of seconds, this method returns the corresponding DateTime object.

I think there's a problem when you define a count that does not skip leap seconds, and uses the local timezone. Don't do that.

Support for this module is provided via the [email protected] email list. See http://lists.perl.org/ for more details.

Eugene van der Pijll <[email protected]>

Copyright (c) 2003-2006 Eugene van der Pijll. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

DateTime

[email protected] mailing list