summaryrefslogtreecommitdiff
path: root/doc/libstddjb/tai.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/libstddjb/tai.html')
-rw-r--r--doc/libstddjb/tai.html26
1 files changed, 13 insertions, 13 deletions
diff --git a/doc/libstddjb/tai.html b/doc/libstddjb/tai.html
index efd4346..d3eaa1d 100644
--- a/doc/libstddjb/tai.html
+++ b/doc/libstddjb/tai.html
@@ -50,21 +50,21 @@ understand what is going on:
</p>
<ul>
- <li> <a href="http://www.madore.org/~david/misc/time.html">David Madore's page
+ <li> <a href="https://www.madore.org/~david/misc/time.html">David Madore's page
on time</a>. It's outdated (there was a leap second in 2009), but complete. </li>
<li> From David Madore again, more to the point: a
-<a href="http://www.madore.org/~david/computers/unix-leap-seconds.html">page
+<a href="https://www.madore.org/~david/computers/unix-leap-seconds.html">page
about leap seconds, UTC and TAI</a>. </li>
<li> The skalibs <a href="../flags.html#clockistai">--enable-tai-clock</a>
documentation. </li>
- <li> <a href="http://cr.yp.to/proto/utctai.html">Dan J. Bernstein's page
+ <li> <a href="https://cr.yp.to/proto/utctai.html">Dan J. Bernstein's page
on UTC, TAI and Unix time</a>. </li>
</ul>
<p>
The meat and potatoes of all this is that programmers cannot simply rely on
standard Unix APIs such as
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/gettimeofday.html">gettimeofday()</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/gettimeofday.html">gettimeofday()</a>
(which, by the way, is marked as obsolescent, but it's not going to disappear tomorrow)
to measure time intervals or even to give precise absolute time, and in
any case those APIs will become obsolete in 2038.
@@ -74,7 +74,7 @@ any case those APIs will become obsolete in 2038.
<p>
<tt>tai</tt> implements - among other things - the
-<a href="http://cr.yp.to/libtai/tai64.html">TAI64 and TAI64N</a>
+<a href="https://cr.yp.to/libtai/tai64.html">TAI64 and TAI64N</a>
formats, which are used in all of skalibs. This gives a programmer access
to precise <em>linear absolute time</em>, which is suitable for both
timestamping (<em>wallclock</em> usage) and time interval measurements
@@ -84,7 +84,7 @@ represent dates exceeding the estimated lifespan of the universe).
<p>
<tt>tai</tt> has been inspired by Dan J. Bernstein's
-<a href="http://cr.yp.to/libtai.html">libtai</a> library, but does not
+<a href="https://cr.yp.to/libtai.html">libtai</a> library, but does not
borrow any code from it.
</p>
@@ -96,10 +96,10 @@ precision. A <tt>tain_t</tt> structure holds an absolute date with a
maximum of one-nanosecond precision, as permitted by the underlying system
call. If <a href="../flags.html#usert">flag-usert</a> is clear, the system
clock will be read via
-<a href="http://www.opengroup.org/onlinepubs/9699919799/functions/gettimeofday.html">gettimeofday()</a>
+<a href="https://www.opengroup.org/onlinepubs/9699919799/functions/gettimeofday.html">gettimeofday()</a>
system call, which has a one-microsecond precision; if it is set, the
system clock will be read via the
-<a href="http://www.opengroup.org/onlinepubs/9699919799/functions/clock_gettime.html">clock_gettime()</a>
+<a href="https://www.opengroup.org/onlinepubs/9699919799/functions/clock_gettime.html">clock_gettime()</a>
system call, which has a one-nanosecond precision. In either case, a current
<tt>tain_t</tt> will be unable to be more precise than the underlying
implementation.
@@ -180,7 +180,7 @@ start of a program.
<p>
The following two operations can only succeed if your system provides the
-<a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_gettime.html">clock_gettime()</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_gettime.html">clock_gettime()</a>
primitive with at least one of the CLOCK_MONOTONIC or CLOCK_BOOTTIME clocks.
Otherwise, they will fail with errno set to ENOSYS.
</p>
@@ -333,7 +333,7 @@ depending on whether skalibs was
compiled with the --enable-tai-clock configure option).
This is useful to get valid TAI/TAI64N timestamps out of
information exported by the system, for instance the time_t
-returned by <a href="http://pubs.opengroup.org/onlinepubs/9699919799/functions/time.html">time()</a>,
+returned by <a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/time.html">time()</a>,
or in the <tt>st_atim</tt>, <tt>st_mtim</tt> or
<tt>st_ctim</tt> fields of a <tt>struct stat</tt>.
</p>
@@ -427,14 +427,14 @@ Those functions return nonzero iff *<em>t1</em> is lesser than *<em>t2</em>.
Marshals *<em>t</em> into the buffer <em>s</em> points to, which
must be preallocated with at least TAI_PACK (8) characters. Afterwards,
the buffer contains the
-<a href="http://cr.yp.to/libtai/tai64.html#tai64">external TAI64 format</a>
+<a href="https://cr.yp.to/libtai/tai64.html#tai64">external TAI64 format</a>
representation of *<em>t</em>.
</p>
<p>
<code> void tai_unpack (char const *s, tai_t *t) </code> <br />
Unmarshals the
-<a href="http://cr.yp.to/libtai/tai64.html#tai64">external TAI64 format</a>
+<a href="https://cr.yp.to/libtai/tai64.html#tai64">external TAI64 format</a>
label pointed to by <em>s</em> (at least TAI_PACK characters) and stores
the result into <em>t</em>.
</p>
@@ -443,7 +443,7 @@ the result into <em>t</em>.
<code> void tain_pack (char *s, tain_t const *a) <br />
void tain_unpack (char const *s, tain_t *a) </code> <br />
Same thing with
-<a href="http://cr.yp.to/libtai/tai64.html#tai64n">external TAI64N format</a>,
+<a href="https://cr.yp.to/libtai/tai64.html#tai64n">external TAI64N format</a>,
using TAIN_PACK (12) characters.
</p>