|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0001474 |
[1003.1(2016/18)/Issue7+TC2] System Interfaces |
Editorial |
Clarification Requested |
2021-05-18 14:17 |
2021-12-13 15:13 |
|
|
Reporter |
geoffclare |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Applied |
|
|
|
|
|
Name |
Geoff Clare |
|
Organization |
The Open Group |
|
User Reference |
|
|
Section |
strsignal() |
|
Page Number |
2069 |
|
Line Number |
66341 |
|
Interp Status |
--- |
|
Final Accepted Text |
|
|
|
Summary |
0001474: strsignal() NAME section is misleading |
|
Description |
The NAME section on the strsignal() page says "get name of signal".
This is misleading, as what is returned is not what most readers would think of as the "name" of a signal (which is what the new sig2str() function in Issue 8 draft 2 returns). It should be changed to be consistent with sterror(), which has "get error message string". The use of "message" would also match the text in the strsignal() description that says it uses "the same set of messages as the psignal() function."
|
|
Desired Action |
Change:get name of signal to:get signal message string
|
| Tags |
tc3-2008 |
|
|
Attached Files |
|
|
|
Relationships 
