Content deleted Content added
→time_t parties: express 2^30 as a power instead of longhand; express corresponding time in UTC |
m →History: better "as of" link |
||
Line 260:
The [[2001]] edition of POSIX.1 rectified the faulty leap year rule in the definition of Unix time, but retained the essential definition of Unix time as an encoding of UTC rather than a linear time scale. Also, since the mid-[[1990s]] computer clocks have been routinely set with sufficient precision for this to matter, and they have most commonly been set using the UTC-based definition of Unix time. This has resulted in considerable complexity in Unix implementations, and in the [[Network Time Protocol]], in order to execute steps in the Unix time number whenever leap seconds occur.
As of [[as of 2004|2004]], POSIX has new interfaces making several different time scales available to programs, splitting up the many uses to which Unix times have traditionally been put. The future is one where time values are accompanied by explicit labels of the time scale defining their significance. Unix time as described in this article will still be in wide use for decades to come, but is likely to be increasingly treated as a legacy system and superseded by better-defined systems.
==32-bit overflow==
| |||