Article View: alt.folklore.computers
Article #342Re: An answer to what is the first year of the next century.
From: sa... Sam Bassett RCD
Date: Tue, 19 Dec 1989 20:57
Date: Tue, 19 Dec 1989 20:57
17 lines
1546 bytes
1546 bytes
In article <1989Dec18....@ux1.cso.uiuc.edu> mrch...@ux1.cso.uiuc.edu (Matt Richards ) writes: >Why is everyone tinkering with the end years? Can't we >just define 1 _BC_ to be the first year, since there >was no 0? That would put everything in sync (for AD >at least :-). >"That's not a mistake, that's our system!" No, no, no, no! We simply define a _virtual_ Year 0 of zero length, and thereby rationlaize the would process! Sam'l Bassett, Sterling Software @ NASA Ames Research Center, Moffett Field CA 94035 Work: (415) 694-4792; Home: (415) 969-2644 sa...@well.sf.ca.us sa...@ames.arc.nasa.gov <Disclaimer> := 'Sterling doesn't _have_ opinions -- much less NASA!'
Technical Details
Message-ID:
<4281@amelia.nas.nasa.gov>Path:
mbox-mo1.pugleaf.net!gmdzi!unido!mcsun!uunet!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!mips!apple!bionet!ames!amelia!pioneer.arc.nasa.gov!samlbReferences:
<18494@bellcore.bellcore.com> <552@enea.se> <8483@ttidca.TTI.COM> <1468@skye.ed.ac.uk> <49878@bbn.COM> <1989Dec18.214254.9231@ux1.cso.uiuc.edu>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!gmdzi!unido!mcsun!uunet!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!mips!apple!bionet!ames!amelia!pioneer.arc.nasa.gov!samlb From: sa...@pioneer.arc.nasa.gov (Sam Bassett RCD) Newsgroups: alt.folklore.computers Subject: Re: An answer to what is the first year of the next century. Keywords: Year 0 Message-ID: <4281@amelia.nas.nasa.gov> Date: 19 Dec 89 20:57:43 GMT References: <18494@bellcore.bellcore.com> <552@enea.se> <8483@ttidca.TTI.COM> <1468@skye.ed.ac.uk> <49878@bbn.COM> <1989Dec18.214254.9231@ux1.cso.uiuc.edu> Sender: ne...@amelia.nas.nasa.gov Reply-To: sa...@pioneer.arc.nasa.gov (Sam Bassett RCD) Organization: NASA Ames Research Center, Mtn Vw CA 94035 Lines: 17 Posted: Tue Dec 19 21:57:43 1989 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit