Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!zephyr.ens.tek.com!tekcrl!tekgvs!toma
From: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Bug In Microsoft C 5.1 asctime function?
Message-ID: <6882@tekgvs.LABS.TEK.COM>
Date: 18 Feb 90 00:52:34 GMT
References: <3156@optilink.UUCP>
Reply-To: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 21

In article <3156@optilink.UUCP> cramer@optilink.UUCP (Clayton Cramer) writes:

>The asctime function for converting date and time to the ASCII string
>equivalent seems to fail for years after 2038.  (This should tell
>you what sort of error checking our quality assurance team does,
>and how long we expect our product to be in the field).

Well, how many computer programs written in 1942 (or earlier) are still in
use? How many computers built before 1942 are still in use? Do you *really*
expect your product to still be in use 48 years from now?

>Is this a known bug of asctime?  Does Microsoft intend to fix this
>one anytime soon?

If they are still in business, they *may* fix it in 2037.

(:-) throughout, well mostly throughout.)

Tom Almy
toma@tekgvs.labs.tek.com
Standard Disclaimers Apply