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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9fbc059a74d74032 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-05-31 00:02:13 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!headwall.stanford.edu!news-out.nibble.net!hub1.nntpserver.com!newsfeed.direct.ca!look.ca!newshub2.rdc1.sfba.home.com!news.home.com!news1.rdc1.sfba.home.com.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Leap Seconds References: X-Newsreader: Tom's custom newsreader Message-ID: Date: Thu, 31 May 2001 07:02:12 GMT NNTP-Posting-Host: 24.7.82.199 X-Complaints-To: abuse@home.net X-Trace: news1.rdc1.sfba.home.com 991292532 24.7.82.199 (Thu, 31 May 2001 00:02:12 PDT) NNTP-Posting-Date: Thu, 31 May 2001 00:02:12 PDT Organization: Excite@Home - The Leader in Broadband http://home.com/faster Xref: archiver1.google.com comp.lang.ada:7913 Date: 2001-05-31T07:02:12+00:00 List-Id: >beer at 1,234,567,890.0 seconds after the epoch. It doesn't matter that >my clock shows a different time than yours (because I count leap seconds >and you don't, Absolutely. If we agree, on January 1, 2003, to meet again in 365 days, we will meet on January 1, 2004. If we then agree to meet after another 365 days, we'll meet on December 31, 2004, not on January 1, 2005. But if we agree to meet on New Years Day, we'll meet in both cases on January 1. If we agree to exchange radio signals after N seconds, no problem. If we agree to exchange them daily at midnight, it will make a difference whether we are both modifying our clocks for leap seconds, or not. Leap seconds (or years) has nothing to do with the passage of time, only with the naming of times.