<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>I'll add that while this is the best practice, and is indeed what is implemented in the vast majority of hardware and software I've seen, I've also seen implementations that either advance from 1:59, to 2:00, to 3:01 - or go from 1:59 briefly to 2:00 and
then some fraction of a second later go to 3:00. Both of which I would consider to be bugs.</p>
<p><br>
</p>
<p>This is especially problematic in the fall-back direction when the transition is at or near midnight. Instead of correctly going from 23:59 to 23:00, if one erroneously hits 00:00 before going back, then that means the DATE has changed as well - and then
changes back again a split second later. This can have nasty consequences if there are events triggered to fire right at midnight.</p>
<p><br>
</p>
<p>IIRC, there was a bug in some older versions of Windows (can't recall which) related to this. To avoid a possible regression, the Windows data has all 00:00 fall-back transitions defined as 23:59:59.999 of the prior day.</p>
<div><br>
</div>
-Matt<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> tz-bounces@iana.org <tz-bounces@iana.org> on behalf of Paul Eggert <eggert@cs.ucla.edu><br>
<b>Sent:</b> Wednesday, June 15, 2016 11:47 AM<br>
<b>To:</b> Inman, Mark H CIV USARMY HQDA (US); Time zone mailing list<br>
<b>Subject:</b> Re: [tz] the final second before standard time daylight savings time transitions</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Inman, Mark H CIV USARMY HQDA (US) wrote:<br>
> Is there any official documentation on the time zone for March 13 2016 in<br>
> New York City, when the clock says 1:59:59.99991000 ?<br>
<br>
I don't know about "official", but in practice digital clocks jump from <br>
01:59:59.99999...9 EST to 03:00:00 EDT. You can use as many 9s as you want, as <br>
long as it's a finite number of 9s. This is baked into the POSIX API, e.g., the <br>
nanoseconds component of struct timespec has nine 9s.<br>
<br>
This reminds me of the confusion at midnight. Does midnight belong to the <br>
previous day, to the next day, to both, or to neither? Traditionally, it was <br>
ambiguous. Nowadays with digital clocks midnight is invariably 00:00 at the <br>
start of the next day.<br>
</div>
</span></font></div>
</div>
</body>
</html>