All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vincent Lefevre <vincent-buymaDBGzMOsTnJN9+BGXg@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: clock(3) man page: precision vs accuracy
Date: Sat, 13 Sep 2014 19:33:19 -0700	[thread overview]
Message-ID: <5414FE6F.2030603@gmail.com> (raw)
In-Reply-To: <20140912120804.GE4404-Ljv1qFl2dU+MDATNRQa/ww@public.gmane.org>

On 09/12/2014 05:08 AM, Vincent Lefevre wrote:
> http://man7.org/linux/man-pages/man3/clock.3.html contains:
> 
>        In glibc 2.17 and earlier, clock() was implemented on top of
>        times(2).  For improved precision, since glibc 2.18, it is
>                       ^^^^^^^^^^^^^^^^^^
>        implemented on top of clock_gettime(2) (using the
>        CLOCK_PROCESS_CPUTIME_ID clock).
> 
> This looks strange. The user doesn't seek improved precision, but
> improved accuracy: if one gets more digits but the value itself is
> less accurate (i.e. the error against the ideal value is larger),
> this is bad. Perhaps changing "precision" to "accuracy" would be
> correct (I assume that the real goal of the change was not just
> improved precision, but more importantly the resulting improved
> accuracy). I've reported a bug about the glibc documentation:
> 
>   https://sourceware.org/bugzilla/show_bug.cgi?id=17383

It looks to me like your supposition is correct, Vincent.
I have changed "precision" to "accuracy".

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2014-09-14  2:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12 12:08 clock(3) man page: precision vs accuracy Vincent Lefevre
     [not found] ` <20140912120804.GE4404-Ljv1qFl2dU+MDATNRQa/ww@public.gmane.org>
2014-09-14  2:33   ` Michael Kerrisk (man-pages) [this message]

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=5414FE6F.2030603@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vincent-buymaDBGzMOsTnJN9+BGXg@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.