diff options
| author | Dag-Erling Smørgrav <des@FreeBSD.org> | 2025-12-11 10:28:59 +0000 |
|---|---|---|
| committer | Dag-Erling Smørgrav <des@FreeBSD.org> | 2025-12-11 10:28:59 +0000 |
| commit | 0d46d875e60091694abe5d38e0cbb4c8019bfd71 (patch) | |
| tree | 5d52afe9fe7ccb0e9f4357ab8e9926be47b129a3 /time2posix.3.txt | |
| parent | 76d3e9d6b36023210e896d00ecef2d19f0acd2d8 (diff) | |
Diffstat (limited to 'time2posix.3.txt')
| -rw-r--r-- | time2posix.3.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/time2posix.3.txt b/time2posix.3.txt index 87789b366978..6b0e0449b816 100644 --- a/time2posix.3.txt +++ b/time2posix.3.txt @@ -20,12 +20,12 @@ DESCRIPTION If the time package is configured with leap-second support enabled, however, no such adjustment is needed and time_t values continue to - increase over leap events (as a true "seconds since..." value). This + increase over leap events (as a true “seconds since...” value). This means that these values will differ from those required by POSIX by the net number of leap seconds inserted since the Epoch. Typically this is not a problem as the type time_t is intended to be - (mostly) opaque - time_t values should only be obtained-from and + (mostly) opaque – time_t values should only be obtained-from and passed-to functions such as time(2), localtime(3), mktime(3), and difftime(3). However, POSIX gives an arithmetic expression for directly computing a time_t value from a given date/time, and the same |