Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
0001475 |
[Issue 8 drafts] System Interfaces |
Editorial |
Clarification Requested |
2021-05-19 01:36 |
2021-06-22 08:52 |
|
Reporter |
cmsmith |
View Status |
public |
|
Assigned To |
|
Priority |
normal |
Resolution |
Accepted |
|
Status |
Applied |
|
Product Version |
Draft 2 |
|
Name |
Curtis Smith |
Organization |
|
User Reference |
|
Section |
socket(), shutdown() |
Page Number |
1898, 1953 |
Line Number |
61830-61837, 63555 |
Final Accepted Text |
|
|
Summary |
0001475: socket() and shutdown() should refer to close() |
Description |
The socket() function description does not mention that the file descriptor returned should eventually be closed with the close() function. The see-also section mentions several related functions such as shutdown() but omits close(), and a reader may wrongly conclude that the proper way to relinquish the resources obtained through socket() is to merely call shutdown() as the shutdown() description makes no mention of close() as well.
|
Desired Action |
In the shutdown() Application Usage, line 61830, replace "None" with "The file descriptor remains open after shutdown() returns to the calling application."
In the "See Also" sections for shutdown() and socket(), add a reference to the close() function. |
Tags |
issue8 |
|
Attached Files |
|
|