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-30 09:36:47 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!cyclone.bc.net!newsfeed.direct.ca!look.ca!border1.nntp.aus1.giganews.com!nntp2.aus1.giganews.com!news-east.rr.com!news-west.rr.com!news.rr.com!news-west.rr.com!lsnws01.we.mediaone.net!cyclone-LA3.rr.com!typhoon.san.rr.com.POSTED!not-for-mail Message-ID: <3B15219E.AAB23A2F@san.rr.com> From: Darren New Organization: Boxes! X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Leap Seconds References: <9elpii$30i$1@nh.pace.co.uk> <3B0ED67B.E40A4E06@averstar.com> <9f0ciq$itb$1@nh.pace.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 30 May 2001 16:36:46 GMT NNTP-Posting-Host: 24.94.20.169 X-Complaints-To: abuse@rr.com X-Trace: typhoon.san.rr.com 991240606 24.94.20.169 (Wed, 30 May 2001 09:36:46 PDT) NNTP-Posting-Date: Wed, 30 May 2001 09:36:46 PDT Xref: archiver1.google.com comp.lang.ada:7885 Date: 2001-05-30T16:36:46+00:00 List-Id: Arthur Evans Jr wrote: > I expect that an Ada program that communicates with an unmanned > (unpersoned?) space ship might care very much indeed. Not really. Firstly, I'd be surprised if an uncompensated clock on an unprotected spaceship actually stayed accurate to a half-second over the lifetime of its mission. I could be wrong, there. Leap seconds are really only a problem when calculating intervals between two declared dates. If you want to know the number of seconds since some epoch, leap seconds might make a difference. If you want to know when it's some number of seconds since you launched the spaceship, the spaceship doesn't need to know about leap seconds, and neither does ground control if they don't adjust their own clock for leap seconds. Leap seconds are there to make midnight be "the same time" every day just like leap days are there to make Jan 1 be the same time every year. > Here the problem is not one Ada can solve. You would need a clock > at the receiving station that either was never corrected for leap > seconds, or you would need a table of corrections. Given clock drift, I don't imagine either of these would be adiquate. -- Darren New / Senior MTS & Free Radical / Invisible Worlds Inc. San Diego, CA, USA (PST). Cryptokeys on demand. This is top-quality raw fish, the Rolls-Rice of Sushi!