Re: [LEAPSECS] POSIX? (was Time math libraries, UTC to TAI)

2016-12-29 Thread Harlan Stenn
Rob, You are way more polite than I might be. I do believe, however, that NTF's General Timestamp API project might help POSIX out here, in that it can map other timescales to UTC, although going the other direction means one has to know how the POSIX system handles leap seconds. POSIX needs at

Re: [LEAPSECS] POSIX? (was Time math libraries, UTC to TAI)

2016-12-29 Thread Rob Seaman
On Dec 29, 2016, at 1:35 PM, Warner Losh wrote: >> A lot of code could have been changed while the ITU fiddled, e.g., Mac OS X >> was launched in 2001. > > Could have, but didn’t... > > Of course, MacOS is largely based on legacy code... Sixteen years ago, MacOS was a completely different oper

Re: [LEAPSECS] POSIX? (was Time math libraries, UTC to TAI)

2016-12-29 Thread Warner Losh
On Thu, Dec 29, 2016 at 4:29 AM, Rob Seaman wrote: > Warner is staging a spirited defense of POSIX. Such a stalwart champion > deserves a more worthy cause. > > POSIX time_t says they don't exist. Therefore, they don't exist. > > > POSIX, meet physics. There's nothing that says that DUT1 < 0.9 is

Re: [LEAPSECS] Time math libraries, UTC to TAI

2016-12-29 Thread Steve Summit
Warner Losh wrote: > On Thu, Dec 29, 2016 at 12:28 AM, Steve Summit wrote: >> If we try to handle them better, two conclusions seem inescapable: >> >> 1. Posix-compatible time_t values will need to be smeared, >>spreading the leap second out more gradually, to eliminate >>sudden, unseemly

Re: [LEAPSECS] Time math libraries, UTC to TAI

2016-12-29 Thread Steve Allen
On Thu 2016-12-29T09:26:58 -0700, Warner Losh hath writ: > How do you deal with acquiring knowledge of leap seconds after you've > given out 'old' timestamps that might be affected by them? This is > best described as how well you recover from the leapsecond file being > corrupted and replaced, tho

Re: [LEAPSECS] Time math libraries, UTC to TAI

2016-12-29 Thread Warner Losh
On Thu, Dec 29, 2016 at 12:28 AM, Steve Summit wrote: > If we try to handle them better, two conclusions seem inescapable: > > 1. Posix-compatible time_t values will need to be smeared, >spreading the leap second out more gradually, to eliminate >sudden, unseemly jumps. > > 2. There needs

[LEAPSECS] POSIX? (was Time math libraries, UTC to TAI)

2016-12-29 Thread Rob Seaman
Warner is staging a spirited defense of POSIX. Such a stalwart champion deserves a more worthy cause. > POSIX time_t says they don't exist. Therefore, they don't exist. POSIX, meet physics. > There's millions of lines of code written to POSIX with the mistaken > assumption that they are imple