View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000678 | 1003.1(2008)/Issue 7 | Base Definitions and Headers | public | 2013-04-12 22:21 | 2019-06-10 08:55 |
| Reporter | jokearney | Assigned To | ajosey | ||
| Priority | normal | Severity | Editorial | Type | Enhancement Request |
| Status | Closed | Resolution | Accepted | ||
| Name | John Kearney | ||||
| Organization | |||||
| User Reference | tmpfile.iso.c | ||||
| Section | tmpfile | ||||
| Page Number | 2121 | ||||
| Line Number | 67136 | ||||
| Interp Status | --- | ||||
| Final Accepted Text | see Desired Action | ||||
| Summary | 0000678: Update tmpfile defintion to line up with ISO c88/89 c99 c11 | ||||
| Description | http://pubs.opengroup.org/onlinepubs/9699919799/functions/tmpfile.html The following is miss-leading, "The file is opened as in fopen() for update (w+)" All versions of ISO c specify that the file should be opened as binary as such it should read The file is opened as in fopen() for update (wb+). This is already implicitly the case as it defers to the ISO-C standard. | ||||
| Desired Action | Request that the following text be updated in line with ISO C The tmpfile() function shall create a temporary file and open a corresponding stream. The file shall be automatically deleted when all references to the file are closed. The file is opened as in fopen() for update (w+), except that implementations may restrict the permissions, either by clearing the file mode bits or setting them to the value S_IRUSR | S_IWUSR. to The tmpfile() function shall create a temporary file and open a corresponding stream. The file shall be automatically deleted when all references to the file are closed. The file is opened as in fopen() for update (wb+), except that implementations may restrict the permissions, either by clearing the file mode bits or setting them to the value S_IRUSR | S_IWUSR. | ||||
| Tags | tc2-2008 | ||||
|
|
Note that POSIX already has a <CX> requirement that for fopen(), "w+' and "wb+" behave identically in POSIX (it is only in C99 where they are not required to be identical, which is why the wb+ matters there). As such, your change is an editorial matter, and not a change in requirements; but I still agree that it makes sense for a minimum of confusion for people referring to POSIX documentation even on a non-POSIX system where binary files differ from text files. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-04-12 22:21 | jokearney | New Issue | |
| 2013-04-12 22:21 | jokearney | Status | New => Under Review |
| 2013-04-12 22:21 | jokearney | Assigned To | => ajosey |
| 2013-04-12 22:21 | jokearney | Name | => John Kearney |
| 2013-04-12 22:21 | jokearney | User Reference | => tmpfile.iso.c |
| 2013-04-12 22:21 | jokearney | Section | => (section number or name, can be interface name) |
| 2013-04-12 22:21 | jokearney | Page Number | => (page or range of pages) |
| 2013-04-12 22:21 | jokearney | Line Number | => (Line or range of lines) |
| 2013-04-12 22:28 | eblake | Note Added: 0001539 | |
| 2013-04-18 16:12 | eblake | Interp Status | => --- |
| 2013-04-18 16:12 | eblake | Final Accepted Text | => see Desired Action |
| 2013-04-18 16:12 | eblake | Status | Under Review => Resolved |
| 2013-04-18 16:12 | eblake | Resolution | Open => Accepted |
| 2013-04-18 16:12 | eblake | Tag Attached: tc2-2008 | |
| 2013-04-18 16:13 | eblake | Section | (section number or name, can be interface name) => tmpfile |
| 2013-04-18 16:13 | eblake | Page Number | (page or range of pages) => 2121 |
| 2013-04-18 16:13 | eblake | Line Number | (Line or range of lines) => 67136 |
| 2019-06-10 08:55 | agadmin | Status | Resolved => Closed |
