|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0001359 |
[Issue 8 drafts] System Interfaces |
Comment |
Error |
2020-06-30 15:14 |
2024-06-11 09:12 |
|
|
Reporter |
geoffclare |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Closed |
|
Product Version |
Draft 1 |
|
|
Name |
Geoff Clare |
|
Organization |
The Open Group |
|
User Reference |
|
|
Section |
dirfd() |
|
Page Number |
712 |
|
Line Number |
24548 |
|
Final Accepted Text |
|
|
|
Summary |
0001359: dirfd() rationale out of date |
|
Description |
Bug 0000391 made changes to the normative text for dirfd() but did not update the RATIONALE to match.
|
|
Desired Action |
Change:The description uses the term ``a file descriptor'' rather than ``the file descriptor''. The implication intended is that an implementation that does not use an fd for opendir() could still open() the directory to implement the dirfd() function. Such a descriptor must be closed later during a call to closedir().
If it is necessary to allocate an fd to be returned by dirfd(), it should be done at the time of a call to opendir(). to:On an implementation where reading from a directory stream does not use a file descriptor, opendir() need not allocate one to be returned by dirfd(). The implementation can instead delay the allocation of a suitable file descriptor until the first time dirfd() is called for the stream. A file descriptor allocated by dirfd() must be closed by closedir().
|
| Tags |
issue8 |
|
|
Attached Files |
|
|
|
Relationships 
