|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0000747 |
[1003.1(2013)/Issue7+TC1] System Interfaces |
Editorial |
Error |
2013-09-07 02:57 |
2019-06-10 08:55 |
|
|
Reporter |
dalias |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Closed |
|
|
|
|
|
Name |
Rich Felker |
|
Organization |
musl libc |
|
User Reference |
|
|
Section |
pthread_once |
|
Page Number |
1685 |
|
Line Number |
54534-54535 |
|
Interp Status |
--- |
|
Final Accepted Text |
|
|
|
Summary |
0000747: Confusing erroneous text about address-of-array in pthread_once rationale |
|
Description |
The rationale text for pthread_once contains:
"Note that a pthread_once_t cannot be an array because some compilers do not accept the construct &<array_name>."
Presumably this is cruft from an ancient version of the Threads standard that was not aligned with ISO C.
Not only is the remark false for all conforming C compilers; it is confusing/misleading to have such text that seems to impose normative requirements ("cannot be") in a non-normative section. Moreover, even if ISO C did permit compilers to reject this construct, the need to avoid defining pthread_once_t with array type would apply only to implementations making use of such compilers, not to all implementations.
|
|
Desired Action |
Remove the text:
"Note that a pthread_once_t cannot be an array because some compilers do not accept the construct &<array_name>."
from the rationale for pthread_once.
|
| Tags |
tc2-2008 |
|
|
Attached Files |
|
|
|
Relationships 
