Actually, that a Y100K problem.

Hopefully, we'll have a fix during the next 97990+ years.

-----Original Message-----
From: Kevin Kenny [mailto:kevin.b.kenny@[...].com]
Sent: Wednesday, November 04, 2009 3:38 PM
To: Perez, Aaron P.
Cc: Andreas Kupries; Wunderlich, Thomas; Jeff Hobbs; Activetcl ML
Subject: Re: [Activetcl] FW: highest allowed clock value?

Perez, Aaron P. wrote:
>  Here's what I found just playing around with [clock scan [clock format]].
> 
> 
> 
>  Running various numbers through I maxed out at
> 
>  clock scan [clock format 3093528009599]
> 
> 
> 
>  If, however, I put in 3093528009600 I get
> 
>  unable to convert date-time string "Sat Jan 01 00:00:00 PST 100000"
> 
> 
> 
>  I then ran clock format 3093528009599 by itself and get the date-time
>  string above 01/01/100000 @ 00:00:00.
> 
>  So it looks like some clock options don't take the same data width as
>  others.

Yes, [clock scan] has a Y10K problem.  I'm planning to let posterity
worry about that one.

Kevin

CONFIDENTIALITY STATEMENT. This email and any attachment is for the sole use of the intended
 recipient and may contain private, confidential and/or privileged information that may be s
ubject to Hospira internal policies. If you are not the intended recipient, any disseminatio
n, distribution or copying is strictly prohibited. If you have received this transmission in
 error, please notify Hospira immediately by return email or by email to privacypostmaster@[
...].com and delete the message and all copies and attachments from your system.
_______________________________________________
ActiveTcl mailing list
ActiveTcl@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs