Path: utzoo!utgpu!water!watmath!clyde!rutgers!ucsd!ucbvax!ucsfcgl!cca.ucsf.edu!rk9005
From: rk9005@cca.ucsf.edu (Roland McGrath)
Newsgroups: comp.lang.c
Subject: Re: Timekeeping in ANSI C
Message-ID: <1152@ucsfcca.ucsf.edu>
Date: 12 Feb 88 03:58:32 GMT
References: <461@auvax.UUCP> <28700025@ccvaxa> <7159@brl-smoke.ARPA> <2527@haddock.ISC.COM> <594@acornrc.UUCP> <2079@bsu-cs.UUCP>
Reply-To: roland@rtsg.lbl.gov (Roland McGrath)
Organization: Hackers Anonymous International, Ltd., Inc. (Applications welcome)
Lines: 16

["Timekeeping in ANSI C"] - dhesi@bsu-cs.UUCP (Rahul Dhesi):
} Sooner than you can say "UNIX is a Trademark of ...", 47000 AD will be
} here.  The greatest mistake a designer can make is to assume that a
} certain date and time will never come.  Such short-sightedness has
} caused problems over and over again, yet we see it again and again.
} Just recently we heard about chaos in the DEC-20 world because they had
} to extend their time structure and use up some reserved fields that
} people had already begun to use for other things.

If we're still using Unix (or POSIX, or GNU) in AD 47000,
or even 2038, I will do repeated belly-flips in my grave (or
perhaps in my armchair in the case of the latter).
-- 
		Roland McGrath
UUCP: 			...!ucbvax!lbl-rtsg.arpa!roland
ARPA:	 		roland@rtsg.lbl.gov