The following issue has been SUBMITTED. ====================================================================== https://www.austingroupbugs.net/view.php?id=1783 ====================================================================== Reported By: dannyniu Assigned To: ====================================================================== Project: 1003.1(2016/18)/Issue7+TC2 Issue ID: 1783 Category: Rationale Type: Error Severity: Editorial Priority: normal Status: New Name: DannyNiu/NJF Organization: <individual> User Reference: c181.pdf Section: B2.9.1 Thread-Safety Page Number: 3647 Line Number: 124665-124666 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2023-10-18 04:21 UTC Last Modified: 2023-10-18 04:21 UTC ====================================================================== Summary: This sentence from this section is discussing thread safety isn't it? Description: At the aforementioned lines, this is said:
> As it turns out, some functions are inherently not thread-safe; that is, their interface specifications preclude async-signal-safety. Notice towards the end of this sentence, it says "async-signal-safety". However, this section is dealing with "thread safety", so I think this is probably a typo. Desired Action: Change "async-signal-safety" to "thread-safety" if that's what's actually intended. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2023-10-18 04:21 dannyniu New Issue 2023-10-18 04:21 dannyniu Name => DannyNiu/NJF 2023-10-18 04:21 dannyniu Organization => <individual> 2023-10-18 04:21 dannyniu User Reference => c181.pdf 2023-10-18 04:21 dannyniu Section => B2.9.1 Thread-Safety 2023-10-18 04:21 dannyniu Page Number => 3647 2023-10-18 04:21 dannyniu Line Number => 124665-124666 ======================================================================
