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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: =?UTF-8?Q?Bj=c3=b6rn_Lundin?= Newsgroups: comp.lang.ada Subject: Re: 'Leap Second' to Be Added on New Year's Eve This Year Date: Fri, 13 Jan 2017 10:24:21 +0100 Organization: A noiseless patient Spider Message-ID: References: <5f5afd36-1ba2-f4e2-62ef-57a652f3170c@verizon.net> <5873c46b.1761953@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Date: Fri, 13 Jan 2017 09:22:43 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="a346a2ef6621922f3d759ff3a22c0487"; logging-data="6254"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/CeMHgJHhDICnNGntFRItP" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.5.1 In-Reply-To: Cancel-Lock: sha1:01dBFyNfe2dy9RYQC3MjUlr/abM= Xref: news.eternal-september.org comp.lang.ada:33093 Date: 2017-01-13T10:24:21+01:00 List-Id: On 2017-01-13 07:51, Tim wrote: >> > Speaking as a former programmer, for 99.9% of the programs out there, > adding a Leap Second doesn't really mean anything. Where it gets > interesting is when the program is dealing with seconds and portions of > seconds - sometimes very minute portions of seconds. Then one had to look > very closely at how one handles things. (just saw that I replied to not c.l.a) Or just something trivial as church bells Story in Swedish but the geist of it is that the church bells were ringing early in the morning (just after midnight that is) Jan 2nd and not Jan 1st The bells should ring in the new year, but failed. This is the first time a computer controlled the ringing. Now- I think the program was polling the time, and when it polled 00:00:01 - and checked the date, it actually found 23:59:60 and concluded that this is the wrong day => do not start ringing. The day after - at 00:00:01 it did the same thing, and the bells started to ring in the new year - 24 hours too late... Yes - I speculate - but I don't think leap seconds only affect super-duper-time-sensitive calcuations. -- Björn