Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!brl-tgr!ron
From: ron@brl-tgr.ARPA (Ron Natalie <ron>)
Newsgroups: net.bugs,net.flame,net.puzzle
Subject: Re: Computer bugs in the year 2000
Message-ID: <7769@brl-tgr.ARPA>
Date: Sun, 27-Jan-85 18:19:06 EST
Article-I.D.: brl-tgr.7769
Posted: Sun Jan 27 18:19:06 1985
Date-Received: Tue, 29-Jan-85 06:55:57 EST
References: <820@reed.UUCP> <5565@rochester.UUCP>
Organization: Ballistic Research Lab
Lines: 14
Xref: watmath net.bugs:521 net.flame:8101 net.puzzle:528

> 
> 	Spencer L. Bolles:
> 	"... He is a programmer and has this notion that when we reach the
> 	year 2000, computers will not accept the new date.  Will the computers
> 	assume that it is 1900, or will it even cause a problem? ..."
> 
> Hey!  No big deal!  So what if every piece of code that prints dates with
> ctime[3] starts believing every year in the 21st century is Year 2, thanks to
> a little parenthesization error?
> 
> 		cp[2] = '0' + t->tm_year >= 200;
> 
Of course, UNIX time (seconds past midnight GMT 1 Jan 1970 in 32 bits)
falls apart around 2042.