In message <[email protected]>, Ian Batten writes : >However, with or without leapseconds, Posix time is still monotonic >both in time_t and , and I would be incredibly dubious of systems >that perform interval timing using ctime or localtime or gmtime, >rather than the raw time_t.
time_t is not guaranteed to be monotonic. If you want a monotonic timestamp nobody messes with, you want to call clock_gettime(CLOCK_MONOTONIC,...) which returns a timestamp that is _not_ referenced to any timescale, but which *is* guaranteed to be monotonic. >> That is why, we cannot have some POSIX systems inserting leap-seconds in >> to time_t and some POSIX systems not doing so. > >I don't think that's the discussion, is it? It very much is, without a 10-20 year leap-second horizon, there is no way we can teach time_t or the time_t successor about leapseconds, and live up to the POSIX "isolated system" requirement. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ LEAPSECS mailing list [email protected] http://six.pairlist.net/mailman/listinfo/leapsecs
