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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no 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 08:35:49 PST Path: archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!isdnet!psinet-france!psiuk-f4!psiuk-p4!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Leap Seconds Date: Thu, 31 May 2001 11:26:24 -0400 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: <9f5nr3$j6m$1@nh.pace.co.uk> References: <9elpii$30i$1@nh.pace.co.uk> <3B0ED67B.E40A4E06@averstar.com><9f0ciq$itb$1@nh.pace.co.uk><9f2ue6$hcm$1@nh.pace.co.uk> <9f347i$jo1$1@nh.pace.co.uk> NNTP-Posting-Host: 136.170.200.133 X-Trace: nh.pace.co.uk 991322787 19670 136.170.200.133 (31 May 2001 15:26:27 GMT) X-Complaints-To: newsmaster@pace.co.uk NNTP-Posting-Date: 31 May 2001 15:26:27 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:7935 Date: 2001-05-31T15:26:27+00:00 List-Id: Yeah - once you're talking just seconds, that's fine because you are now in relative time WRT some epoch. However, once you go to calendar time, you've got a problem. Consider that we agree to meet on March 1. If you count leap years and I don't, won't we have a difference in what the number of days is between now and March 1? So if your epoch is 1/6/80-00:00:00 and my epoch is 1/1/96-00:00:00, how many seconds are between those to epochs? Won't it matter if you count leap-seconds (leap-years?) or not? Naturally, being both in the past, the conversion is a constant value. But what if I need to know the seconds between either of those epochs and some date way in the future? Unlike leap-years, leap-seconds are not predictable. MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com Web: http://www.mcondic.com/ "Robert A Duff" wrote in message news:wccsnhme0pd.fsf@world.std.com... > I don't get it. If we both agree on when the epoch is, and we have a > way of counting seconds since the epoch, then we can agree to meet for > 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, or because I don't believe in "nightdark wasting time", > or because we're in different time zones, or whatever).