[time-nuts] Mac OS and iOS leap second handling

[Tom Van Baak]

Eric,

You might want to try this thread over on the LEAPSECS list [1]. Yes, 
there's a special list just for leap second nuts so that we don't have 
to discuss them here on time-nuts. You'll find the archives deep, 
fascinating, and often contentious. Practical real life examples like 
your low-cost high-reliability UTC station clock would be most welcome.

/tvb

[1] https://pairlist6.pair.net/mailman/listinfo/leapsecs


On 10/22/2019 3:28 PM, Eric Scace wrote:
>     Maybe someone on the list has a recent and authoritative answer to the following questions.
>
>     I’ve been digging around in “civilian mode” (not an OS X or iOS developer) trying to determine if current Mac OS X and iOS releases handle leap seconds:
> no smearing
> proper display of 23:59:60, etc on the system clock & return of same to appropriate function calls.
>
>     I have not been able to discover a well-documented answer to this question; e.g., video of an OS X/iOS system clock displaying a leap second, or Apple-sourced documentation stating leap second support.
>
>     There are assertions that OS X was built around POSIX and suffers from the limitations of Unix epoch time decisions of long ago. Is that still the case?
>
>     (In contrast, Microsoft docs claim Win 2018 Oct and Win Server 2019 now have leap second support.)
>
> Thanks,
>     — Eric
> _______________________________________________
> time-nuts mailing list --time-nuts at lists.febo.com
> To unsubscribe, go tohttp://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com
> and follow the instructions there.