|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0000014 |
[1003.1(2008)/Issue 7] System Interfaces |
Editorial |
Clarification Requested |
2009-05-12 18:58 |
2009-07-30 15:24 |
|
|
Reporter |
Don Cragun |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
normal |
Resolution |
Accepted As Marked |
|
|
Status |
Resolved |
|
|
|
|
|
Name |
Don Cragun |
|
Organization |
Self |
|
User Reference |
|
|
Section |
fopen() |
|
Page Number |
879 |
|
Line Number |
29227 |
|
Interp Status |
--- |
|
Final Accepted Text |
Note: 0000167 |
|
|
Summary |
0000014: fopen() See Also |
|
Description |
Should the fopen() SEE ALSO list include a pointer to XSH Subclause 2.5 (Standard I/O Streams)?
A discussion on fopen() and open() on the alias today made it clear that the submitter hadn't read the overall description of STDIO streams while trying to figure out how fopen() sets the streams file position indicator.
The standard assumes that users have read XBD clauses 1 through 11 and XSH chauses 1 and 2 before trying to interpret the System Interfaces descriptions in XSH. Obviously this doesn't always happen. |
|
Desired Action |
Note that the issue was discussed, but do not change the standard. |
| Tags |
No tags attached. |
|
|
Attached Files |
|
|
|