public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 218452] New: small clarification clock_getres HISTORY section
Date: Fri, 02 Feb 2024 19:27:48 +0000	[thread overview]
Message-ID: <bug-218452-11311@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=218452

            Bug ID: 218452
           Summary: small clarification clock_getres HISTORY section
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: low
          Priority: P3
         Component: man-pages
          Assignee: documentation_man-pages@kernel-bugs.osdl.org
          Reporter: cquike@arcor.de
        Regression: No

In version 6.04 of the man pages, under the HISTORY section of clock_getres(2)
it is mentioned the following:

"       On  POSIX  systems  on  which  these  functions  are  available, the
symbol _POSIX_TIMERS is defined in <unistd.h> to a value greater than 0.  The
symbols _POSIX_MONOTONIC_CLOCK,
       _POSIX_CPUTIME, _POSIX_THREAD_CPUTIME indicate that CLOCK_MONOTONIC,
CLOCK_PROCESS_CPUTIME_ID, CLOCK_THREAD_CPUTIME_ID are available.  (See also
sysconf(3).)  POSIX.1-2008  makes
       these APIs mandatory.
"

At first read I got the impression that _POSIX_MONOTONIC_CLOCK,      
_POSIX_CPUTIME, _POSIX_THREAD_CPUTIME are also mandatory. However only
_POSIX_TIMERS is mandatory, while the others are still optional according to
the the POSIX online documentation of the last standard ([1], under 2.1.3 POSIX
Conformance).

I would suggest to change it slightly to make clear that only _POSIX_TIMERS is
mandatory in POSIX.1-2008 but _POSIX_MONOTONIC_CLOCK,       _POSIX_CPUTIME,
_POSIX_THREAD_CPUTIME are not and therefore portable applications cannot rely
on those clocks to be available without checking for the corresponding symbols
first.


[1] The Open Group Base Specifications Issue 7, 2018 edition
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap02.html

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2024-02-02 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 19:27 bugzilla-daemon [this message]
2024-03-04 12:05 ` [Bug 218452] small clarification clock_getres HISTORY section bugzilla-daemon

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=bug-218452-11311@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-man@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox