Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
0001783 |
[1003.1(2016/18)/Issue7+TC2] Rationale |
Editorial |
Error |
2023-10-18 04:21 |
2024-06-11 09:07 |
|
Reporter |
dannyniu |
View Status |
public |
|
Assigned To |
|
Priority |
normal |
Resolution |
Accepted |
|
Status |
Closed |
|
|
|
|
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 |
|
|
Summary |
0001783: 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. |
Tags |
applied_after_i8d3, tc3-2008 |
|
Attached Files |
|
|