From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2ed09815e1f9264a X-Google-Attributes: gid103376,public From: Corey Minyard Subject: Re: 5th USENIX Conf on Object-Oriented Tech & Sys (COOTS'99) - CFP Date: 1998/05/16 Message-ID: #1/1 X-Deja-AN: 353839330 Sender: minyard@wf-rch.cirr.com References: <199805141444.QAA10968@basement.replay.com> Organization: Wonderforce Research Newsgroups: comp.lang.ada Date: 1998-05-16T00:00:00+00:00 List-Id: Stephen.Leake@gsfc.nasa.gov writes: > > Who says the next millenium can't start with 2000? That's when most of > the digits change. That's when the 21st century begins (the "century" > is the first two digits of the year, plus one). That's when all the > non-Y2K programs will break. The current millenium started in 1000 AD, > the one before that in 0 AD, the one before that in ... hmm, things > get tricky for BC, but I'll just ignore that. > > -- Stephe There was no 0 AD. We went straight from 1 BC to 1 AD. Apparently, not many C programmers were around to stress the importance of zero :-). Me, I don't really care when the millenium starts. It's fairly arbitrary (except for the Y2K problem, of course). -- Corey Minyard Internet: minyard@acm.org Work: minyard@nortel.ca UUCP: minyard@wf-rch.cirr.com