Re^3: Converting epoch times after 2038

Apparently, it does:

use DateTime                qw( );
use DateTime::Format::Epoch qw( );

my $epoch = DateTime->new( year => 1970, month => 1, day => 1 );
my $formatter = DateTime::Format::Epoch->new( epoch => $epoch );

my $dt = $formatter->parse_datetime( 3700771200 );
print( $dt->strftime( '%x %X' ), "\n" );  # Apr 10, 2087 12:00:00 AM
[download]

Update: Better yet:

use DateTime::Format::Epoch::Unix qw( );

my $dt = DateTime::Format::Epoch::Unix->parse_datetime( 3700771200 );
print( $dt->strftime( '%x %X' ), "\n" );  # Apr 10, 2087 12:00:00 AM
[download]

Comment on Re^3: Converting epoch times after 2038 Select or Download Code

Replies are listed 'Best First'.
Re^4: Converting epoch times after 2038 by kurre_vaxholm (Acolyte) on Apr 05, 2007 at 08:14 UTC
Hi ikegami Thanks for the response. Are you on a 64 bit system or a 32?? Cause 32 bit system can only handle epoch before 2038 (2**32) if they rely on the unix built in timegm..	[reply]
Re: Converting epoch times after 2038 by jonadab (Parson) on Apr 05, 2007 at 10:21 UTC
Cause 32 bit system can only handle epoch before 2038 (2**32) if they rely on the unix built in timegm.. The CPU architecture can be 32 bit, as long as a larger size of value is used for times. The code he posted works for me on FreeBSD, on a 32-bit x86 system. Apr 10, 2087 it says. -- We're working on a six-year set of freely redistributable Vacation Bible School materials.	[reply]
Re^5: Converting epoch times after 2038 by ikegami (Patriarch) on Apr 05, 2007 at 15:09 UTC
Did you try it? WinXP on a 32-bit Pentium 4. Even if the CPU doesn't support 64-bit arithmetic — I don't know whether it does or not — it can still be done by software. Think about it... entire CPUs can be emulated in software. However, I'm guessing the module doesn't use 64-bit arithmetic (hardware or software), but rather floating point numbers. They have 56-bit of precision on my system.	[reply]