View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000721 | 1003.1(2013)/Issue7+TC1 | System Interfaces | public | 2013-07-13 12:16 | 2022-08-11 15:38 |
| Reporter | h3h3h3 | Assigned To | |||
| Priority | normal | Severity | Editorial | Type | Clarification Requested |
| Status | Closed | Resolution | Duplicate | ||
| Name | John Peters | ||||
| Organization | |||||
| User Reference | |||||
| Section | basename, dirname | ||||
| Page Number | 619, 730 | ||||
| Line Number | 21157, 24602 | ||||
| Interp Status | --- | ||||
| Final Accepted Text | |||||
| Summary | 0000721: Internal storage vs static storage | ||||
| Description | The former term appears only in the cited lines, whereas "static storage" is more often used to describe the same thing. | ||||
| Desired Action | In lines 21157 and 24602, change "internal storage" to "static storage". | ||||
| Tags | No tags attached. | ||||
|
|
I think this change would be a change in the wrong direction. "Static storage" implies storage with static storage duration, whereas "internal storage", despite not being defined explicitly, has a common-sense meaning of "storage managed internally by the implementation", which could include static storage, allocated storage, or thread-local storage. As many implementations want to use thread-local storage for such interfaces, changes should not be made that require static storage. |
|
|
In reply to 1678: > "Static storage" implies storage with static storage duration, whereas "internal storage", despite not being defined explicitly, has a common-sense meaning of "storage managed internally by the implementation", which could include static storage, allocated storage, or thread-local storage. This report was not meant to invite semantic discussion of static versus internal. The only information perused in this report is the frequency of usage of each term, and the fact that they are interchangeable in the only two cases where "internal storage" is used. Proof of that is how once "internal" is changed for "static", the affected sections imitate other function return descriptions that either use the term "static storage" explicitly or say something to the effect that the calling program shall not modify the data pointed at by the return value. Because of that, your comment is unrelated and depends on a definition of internal that simply isn't in the standard. I'd advise making another report instead of changing the purpose of this one. |
|
|
It's not my intent to change the purpose of this report, but rather to object to the change requested in it. Right now there is no formal requirement that this (ill-defined) "internal storage" be static, and I believe adding such a requirement would be an unwelcome change to many implementors. I agree that the current language is unclear and ambiguous, and that it should be changed, but not in the manner of the desired-action for this issue report. |
|
|
In reply to 1680: > It's not my intent to change the purpose of this report, but rather to object to the change requested in it. As it stands right now, the two terms are interchangeable, so you can't base an objection on one description being different from the other. If you look at the set of changes as cumulative instead of mutually-exclusive, then my proposal is concerned with consistency of usage of terms, whereas yours is concerned with replacement of terms. I don't see how can you object based on alternative tentative changes that don't conflict with those proposed in this report. > Right now there is no formal requirement that this (ill-defined) "internal storage" be static, and I believe adding such a requirement would be an unwelcome change to many implementors. I concur, but for that to happen you need a distinction between the two terms, and the standard doesn't bear one. I hope you understand. |
|
|
This text has already been changed by the resolution of 0001064. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-07-13 12:16 | h3h3h3 | New Issue | |
| 2013-07-13 12:16 | h3h3h3 | Name | => John Peters |
| 2013-07-13 12:16 | h3h3h3 | Section | => basename, dirname |
| 2013-07-13 12:16 | h3h3h3 | Page Number | => 619, 730 |
| 2013-07-13 12:16 | h3h3h3 | Line Number | => 21157, 24602 |
| 2013-07-13 15:54 | dalias | Note Added: 0001678 | |
| 2013-07-13 16:02 | h3h3h3 | Note Added: 0001679 | |
| 2013-07-13 16:03 | h3h3h3 | Note Edited: 0001679 | |
| 2013-07-13 16:21 | dalias | Note Added: 0001680 | |
| 2013-07-13 16:29 | h3h3h3 | Note Added: 0001681 | |
| 2022-08-11 15:37 | Don Cragun | Relationship added | related to 0001064 |
| 2022-08-11 15:38 | Don Cragun | Interp Status | => --- |
| 2022-08-11 15:38 | Don Cragun | Note Added: 0005931 | |
| 2022-08-11 15:38 | Don Cragun | Status | New => Closed |
| 2022-08-11 15:38 | Don Cragun | Resolution | Open => Duplicate |
