Messages in this thread | | | Date | Wed, 4 Sep 2013 12:20:58 -0700 | Subject | Re: clock_gettime_ns | From | John Stultz <> |
| |
On Wed, Sep 4, 2013 at 11:51 AM, Andy Lutomirski <luto@amacapital.net> wrote: > I think that most of the hangup was a lack of agreement on how the API > should work wrt leap seconds.
I don't recall this objection. The interface uses existing clockids, so it probably should keep the existing leap-second behavior of those clockids.
> I've always thought that the Right Way to represent a UTC time is > nanoseconds since some epoch, where every potential leap second > counts.
Check out the CLOCK_TAI clockid merged in 3.10.
thanks -john
| |