9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Is POSIX:clock_gettime(2) in APE somewhere/anywhere?
Date: Tue, 12 Oct 2021 20:05:51 +0200	[thread overview]
Message-ID: <YWXOfzEsszNP2Q+H@polynum.com> (raw)
In-Reply-To: <YWSE46m1qM3FPQrB@polynum.com>

Le Mon, Oct 11, 2021 at 08:39:31PM +0200, tlaronde@polynum.com a écrit :
>[...] 
> Amongst the extensions I had to add, there are two bits that go beyond
> ISO C libc. One is a way to get elapsed time and unfortunately clock(3)
> is not the answer. I then used POSIX.1:clock_gettime(2) with CLOCK_MONOTONIC
> or CLOCK_REALTIME if the previous is not defined.
> 
> But is clock_gettime(2) available in APE in any instance of Plan9 or is
> there a routine achieving the same purpose?

For what I need, in fact I can simply use nsec(2), diffing nanoseconds
times! (I have the printed manuals from Vita Nuova, I should remember
to read the man pages first in printed form at leisure...)
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
                       http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T1992d89fd8b382c7-M7450a2a55a3baa87b5a2f993
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2021-10-12 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 18:39 tlaronde
2021-10-11 19:12 ` ori
2021-10-12  7:04   ` tlaronde
2021-10-11 19:20 ` Sigrid Solveig Haflínudóttir
2021-10-12  7:05   ` tlaronde
2021-10-12 18:05 ` tlaronde [this message]
2021-10-14 19:58   ` Thaddeus Woskowiak
2021-10-14 21:54 ` ori
2021-10-15 11:15   ` tlaronde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YWXOfzEsszNP2Q+H@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).