The following issue has been SUBMITTED. ====================================================================== https://www.austingroupbugs.net/view.php?id=1781 ====================================================================== Reported By: dannyniu Assigned To: ====================================================================== Project: 1003.1(2016/18)/Issue7+TC2 Issue ID: 1781 Category: Rationale Type: Clarification Requested Severity: Editorial Priority: normal Status: New Name: DannyNiu/NJF Organization: <individual> User Reference: C181.pdf Section: B.2.8 Realtime >> Rationale for the Monotonic Clock Page Number: 3622 Line Number: 123529-123533 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2023-10-17 08:53 UTC Last Modified: 2023-10-17 08:53 UTC ====================================================================== Summary: Factual error due to mis-wording with regard to timed wait functions? Description: At the aforementioned line range, this is said:
> It was decided that the features of CLOCK_MONOTONIC are not as critical to these functions as they are to pthread_cond_timedwait(). The pthread_cond_timedwait() function is given a relative timeout; the timeout may represent a deadline for an event. When these functions are given relative timeouts, the timeouts are typically for error recovery purposes and need not be so precise. The `pthread_cond_timedwait()` is specified with absolute time-outs, and the later sentence doesn't make sense with the earilier parts of the paragraph. It probably should say: > the *other* function is given an absolute timeout; the timeout may represent a deadline for an event. When other functions are given relative timeouts ... typically for error recovery ... Desired Action: Clarify the intended wording. BTW, my previous reported issue should probably be moved to Issue7+TC2 as well, I forgot to select the correct project. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2023-10-17 08:53 dannyniu New Issue 2023-10-17 08:53 dannyniu Name => DannyNiu/NJF 2023-10-17 08:53 dannyniu Organization => <individual> 2023-10-17 08:53 dannyniu User Reference => C181.pdf 2023-10-17 08:53 dannyniu Section => B.2.8 Realtime >> Rationale for the Monotonic Clock 2023-10-17 08:53 dannyniu Page Number => 3622 2023-10-17 08:53 dannyniu Line Number => 123529-123533 ======================================================================
