Path: utzoo!attcan!uunet!dino!ux1.cso.uiuc.edu!brutus.cs.uiuc.edu!apple!amdahl!dacseg
From: dacseg@uts.amdahl.com (Scott E. Garfinkle)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Bug In Microsoft C 5.1 asctime function?
Message-ID: <99m202Ac89QS01@amdahl.uts.amdahl.com>
Date: 20 Feb 90 18:14:20 GMT
References: <6882@tekgvs.LABS.TEK.COM>
Organization: Amdahl Corporation, Sunnyvale CA
Lines: 18

From article <6882@tekgvs.LABS.TEK.COM>, by toma@tekgvs.LABS.TEK.COM (Tom Almy):
> 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).

You would have saved a lot of money in your own time and that of your testing
team (I presume) if you had paid the $150 (or was it $100) for the library
source for their runtimes.  If you really want your product to run after year
2038, just fix the problem yourself.  I know you paid the money, etc., but
presumably you're in business to make money/product, not prod other people's
support departments.

This is *not* meant in any derogatory fashion, just as a suggestion.  I have
found the library sources quite useful, personally.
	-scott e. garfinkle