Path: csiph.com!news.redatomik.org!aioe.org!.POSTED!not-for-mail
From: Kaz Kylheku <221-501-9011@kylheku.com>
Newsgroups: comp.lang.c,comp.programming
Subject: Re: 'Leap Second' to Be Added on New Year's Eve This Year
Date: Fri, 30 Dec 2016 23:26:17 +0000 (UTC)
Organization: Aioe.org NNTP Server
Lines: 26
Message-ID: <20161230152259.382@kylheku.com>
References: <o3gl85$j26$1@dont-email.me> <zKW6A.231838$Uz2.141850@fx29.iad> <mstorkamp-D7E8B5.08341023122016@88-209-239-213.giganet.hu> <o46190$pgl$4@dont-email.me> <msmd6chqmd56ct64c5ac85ov2f74kcpj78@4ax.com>
NNTP-Posting-Host: OGJi3KNpFOhM58UHZwXj0w.user.gioia.aioe.org
X-Complaints-To: abuse@aioe.org
User-Agent: slrn/pre1.0.0-18 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.c:100714 comp.programming:7202

On 2016-12-30, Ken Blake <Ken@invalid.news.com> wrote:
> On Fri, 30 Dec 2016 11:17:59 -0500, Ken Brody <kenbrody@spamcop.net>
> wrote:
>
>>On 12/23/2016 9:34 AM, Mark Storkamp wrote:
>>[...]
>>> Your computers clock doesn't know anything about the leap second, so it
>>> will tick over at midnight New Years just as it does every other night.
>>> When it next connects to a time server it will simply update itself to
>>> the correct time as it always does. However, the official NIST clocks
>>> will, as I understand it, go to 23:59:60.
>>>
>>> I guess if you live in the GMT time zone, you'll need to throw an extra
>>> '1' into the countdown before cheering and throwing streamers.
>>
>>Just "be a programmer" and count to zero rather than 1:
>>
>>    10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!
>
>
> That should be 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, Happy New Year!
>
> Or perhaps, 1001, 1000, 111, 110, 101, 100, 11, 10, 1, 0, Happy New
> Year!

Digital designer: 100, 101, 111, 110, 010, 011, 001, assert HNY.