Date-time module that goes beyond 2023

Date-time module that goes beyond 2023

am 04.12.2008 09:55:09 von Foo JH

Hi all,

The recent discussion on a date-time module leaves me wondering:

Given that time() only works up to year 2023, is there a successor
module which can go beyond 2023, and earlier than 1900?

What will be the code implication to support this new module?

_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Re: Date-time module that goes beyond 2023

am 04.12.2008 11:06:38 von Justin Allegakoen

--===============0261116102==
Content-Type: multipart/alternative;
boundary="----=_Part_3623_19275211.1228385198276"

------=_Part_3623_19275211.1228385198276
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

2008/12/4 Foo JH

> Hi all,
>
> The recent discussion on a date-time module leaves me wondering:
>
> Given that time() only works up to year 2023, is there a successor
> module which can go beyond 2023, and earlier than 1900?
>
> What will be the code implication to support this new module?
>

I think thats actually supposed to be 1st Jan 2038 rather than 2023 (as says
my WinXP 32 bit Centrino):-

print scalar localtime( time + ( 30 * 365 * 24 * 60 * 60 ) );

vs.

print scalar localtime( time + ( 29 * 365 * 24 * 60 * 60 ) );

And AFAIK this only impacts 32 bit machines.


Who knows what will happen by then anyway, my bet is another farcical 'Y2K
bug' causing Intel and M$ shares to rocket through the roof . . .

I should be long gone by then . . . unless my kids try and torture me by
keeping me alive on some yet to be invented life support system

Hopefully by then Jan's, Larry's, Tom's, Gisle's, MJD's (if you feel your
name should be included please add it in - it's starting to get late and
I've had a few too many) brains would be downloadable Matrix style . . . I
think I'd better stop now . . .


Just in

------=_Part_3623_19275211.1228385198276
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


2008/12/4 Foo JH <>

Hi all,



The recent discussion on a date-time module leaves me wondering:



Given that time() only works up to year 2023, is there a successor

module which can go beyond 2023, and earlier than 1900?



What will be the code implication to support this new module?


I think thats actually supposed to be 1st Jan 2038 rather than 2023 (as says my WinXP 32 bit Centrino):-

print scalar localtime( time + ( 30 * 365 * 24 * 60 * 60 ) );

vs.

print scalar localtime( time + ( 29  * 365 * 24 * 60 * 60 ) );


And AFAIK this only impacts 32 bit machines.

<OT>
Who knows what will happen by then anyway, my bet is another farcical 'Y2K bug' causing Intel and M$ shares to rocket through the roof . . .


I should be long gone by then . . . unless my kids try and torture me by keeping me alive on some yet to be invented life support system

Hopefully by then Jan's, Larry's, Tom's, Gisle's, MJD's (if you feel your name should be included please add it in - it's starting to get late and I've had a few too many) brains would be downloadable Matrix style . . . I think I'd better stop now . . .

</OT>

Just in


------=_Part_3623_19275211.1228385198276--

--===============0261116102==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
--===============0261116102==--

RE: Date-time module that goes beyond 2023

am 04.12.2008 16:05:35 von Henry Hartley

Justin Allegakoen wrote:

>> 2008/12/4 Foo JH
>> > The recent discussion on a date-time module leaves me wondering:
>> > Given that time() only works up to year 2023, is there a successor
>> > module which can go beyond 2023, and earlier than 1900?
>> > What will be the code implication to support this new module?
>>
>> I think thats actually supposed to be 1st Jan 2038 rather than 2023
>> (as says my WinXP 32 bit Centrino):-

Time::Local::Extended bumps the cutoff forward to 2098.

--
Henry
_______________________________________________
ActivePerl mailing list
ActivePerl@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs