* Re: 'Leap Second' to Be Added on New Year's Eve This Year [not found] ` <XnsA6FC8C34D75Atimothybilyahoocom@216.166.97.131> @ 2017-01-13 9:24 ` Björn Lundin 2017-01-13 12:51 ` Dennis Lee Bieber 0 siblings, 1 reply; 3+ messages in thread From: Björn Lundin @ 2017-01-13 9:24 UTC (permalink / raw) 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 <https://www.sydsvenskan.se/2017-01-02/kyrkklockorna-ringde-in-aret--i-nio-timmar> 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 'Leap Second' to Be Added on New Year's Eve This Year 2017-01-13 9:24 ` 'Leap Second' to Be Added on New Year's Eve This Year Björn Lundin @ 2017-01-13 12:51 ` Dennis Lee Bieber 2017-01-13 13:47 ` Björn Lundin 0 siblings, 1 reply; 3+ messages in thread From: Dennis Lee Bieber @ 2017-01-13 12:51 UTC (permalink / raw) On Fri, 13 Jan 2017 10:24:21 +0100, Björn Lundin <b.f.lundin@gmail.com> declaimed the following: >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. Could be something as simple as cycling from 23:59:59 to 24:00:00 (still not the "new day") followed by 00:00:01 (new day, but not midnight) -- Wulfraed Dennis Lee Bieber AF6VN wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/ ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 'Leap Second' to Be Added on New Year's Eve This Year 2017-01-13 12:51 ` Dennis Lee Bieber @ 2017-01-13 13:47 ` Björn Lundin 0 siblings, 0 replies; 3+ messages in thread From: Björn Lundin @ 2017-01-13 13:47 UTC (permalink / raw) On 2017-01-13 13:51, Dennis Lee Bieber wrote: > On Fri, 13 Jan 2017 10:24:21 +0100, Björn Lundin <b.f.lundin@gmail.com> > declaimed the following: > >> 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. > > Could be something as simple as cycling from 23:59:59 to 24:00:00 > (still not the "new day") followed by 00:00:01 (new day, but not midnight) > Yes- but suspect that it only happened at leap-second day, and not any other day... -- -- Björn ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-01-13 13:47 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <o3gl85$j26$1@dont-email.me> [not found] ` <op.ytcu9n0djs98qf@red.lan> [not found] ` <5f5afd36-1ba2-f4e2-62ef-57a652f3170c@verizon.net> [not found] ` <o4j73c$345$1@dont-email.me> [not found] ` <op.ytj7fmbnjs98qf@red.lan> [not found] ` <5873c46b.1761953@news.xs4all.nl> [not found] ` <op.yty6zgwijs98qf@red.lan> [not found] ` <XnsA6FC8C34D75Atimothybilyahoocom@216.166.97.131> 2017-01-13 9:24 ` 'Leap Second' to Be Added on New Year's Eve This Year Björn Lundin 2017-01-13 12:51 ` Dennis Lee Bieber 2017-01-13 13:47 ` Björn Lundin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox