Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

nisc wwwxxx, wwwxxx0cm, should producers of software-based services, such as atms, be held liable for economic injuries suffered when their systems fail?, wwwxxx0cm, www.webdp.net, Event 9 IIS log failed to write entry, wwwxxx jeffs, Catastrophic failure Unexpected method call sequence. 0x8000ffff (-2147418113)., ksh lock a file, [unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed

Links

XODOX
Impressum

#1: big problem ahead

Posted on 2007-02-02 10:18:58 by George

# It seems there will be still 32bit cpus with multiple cores that day
# so I do not even think what will happen ...

use strict;
my $now = (split /\s+/,scalar localtime time)[-1];
my $year = (localtime time)[5];
my $total= int 2**32/(365*24*3600);
print $now - $year + $total;

Report this message

#2: Re: big problem ahead

Posted on 2007-02-03 09:58:35 by Joe Smith

George wrote:
> # It seems there will be still 32bit cpus with multiple cores that day
> # so I do not even think what will happen ...
>
> use strict;
> my $now = (split /\s+/,scalar localtime time)[-1];
> my $year = (localtime time)[5];
> my $total= int 2**32/(365*24*3600);
> print $now - $year + $total;

I don't understand why you posted all that.
Everybody knows about the Y2038 "problem".

perl -le 'print scalar gmtime(2**31-1)'
Tue Jan 19 03:14:07 2038

Report this message