View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001781 | 1003.1(2016/18)/Issue7+TC2 | Rationale | public | 2023-10-17 08:53 | 2024-06-11 09:07 |
| Reporter | dannyniu | Assigned To | |||
| Priority | normal | Severity | Editorial | Type | Clarification Requested |
| Status | Closed | Resolution | Accepted As Marked | ||
| 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 | 0001781:0006563 | ||||
| Summary | 0001781: 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. | ||||
| Tags | applied_after_i8d3, tc3-2008 | ||||
|
|
My bad, it (probably should) say: > the pthread_cond_timedwait() 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 ... |
|
|
Change: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.to: The pthread_cond_timedwait() function is given an absolute timeout; the timeout may represent a deadline for an event. When other functions are given relative timeouts, the timeouts are typically for error recovery purposes and need not be so precise. |
| 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 |
| 2023-10-17 09:12 | dannyniu | Note Added: 0006542 | |
| 2023-11-02 15:18 | geoffclare | Note Added: 0006563 | |
| 2023-11-02 15:19 | geoffclare | Interp Status | => --- |
| 2023-11-02 15:19 | geoffclare | Final Accepted Text | => 0001781:0006563 |
| 2023-11-02 15:19 | geoffclare | Status | New => Resolved |
| 2023-11-02 15:19 | geoffclare | Resolution | Open => Accepted As Marked |
| 2023-11-02 15:19 | geoffclare | Tag Attached: tc3-2008 | |
| 2023-11-14 10:41 | geoffclare | Status | Resolved => Applied |
| 2023-11-14 10:41 | geoffclare | Tag Attached: applied_after_i8d3 | |
| 2024-06-11 09:07 | agadmin | Status | Applied => Closed |
