View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001082 | 1003.1(2016/18)/Issue7+TC2 | Shell and Utilities | public | 2016-10-12 08:08 | 2018-04-12 15:36 |
| Reporter | Mark_Galeck | Assigned To | |||
| Priority | normal | Severity | Editorial | Type | Error |
| Status | Closed | Resolution | Rejected | ||
| Name | Mark Galeck | ||||
| Organization | |||||
| User Reference | |||||
| Section | 2.3 Token Recognition | ||||
| Page Number | 2347-2348 | ||||
| Line Number | 74751-74792 | ||||
| Interp Status | --- | ||||
| Final Accepted Text | |||||
| Summary | 0001082: "delimited" is incorrect | ||||
| Description | To "delimit" means, in English, to find both start and end. In Section 2.3 (and perhaps in the rest of the standard, but I am too lazy to check), it is used incorrectly to mean "find end" only. The meaning is clear from context, but it is misleading to an engineer who reads the standard for the first time trying to understand it. Moreover, while the "start" of a token is precisely defined, precisely which character the "end" is, is not. | ||||
| Desired Action | Change: in line 74753, "is delimited" to "ends" in line 74754, "is delimited" to "ends" in line 74755, "be delimited" to "end" in line 74761, "be delimited" to "end with the previous character" in line 74768, "be delimited by" to "end with" in line 74779, "be delimited by" to "end with" in line 74782, "be delimited" to "end with the previous character" in line 74785, "is delimited" to "shall end with it" I am not listing line 74751, because that whole sentence fragment should begone and I will address that in another report. | ||||
| Tags | No tags attached. | ||||
| related to | 0001100 | Closed | Rewrite of Section 2.10 Shell Grammar, of the Shell Standard, to fix previous reports, fix new issues, and improve presentation. |
|
|
Re: To "delimit" means, in English, to find both start and end. Then if something "is delimited" it means we have found both the start and the end, right? The start has been found earlier, so when the end is found, we have found both, and the token "is delimited". I don't think that wording is ether unclear or incorrect, and while I might not write it that way myself, I don't think it's a good idea to go making wording changes that aren't essential for clarity. kre |
|
|
OK, I see your point for those changes that would replace "is/be delimited" with "end(s)" . However, in some cases it is not clear where the token ends - see the 3 changes on lines 74761, 74782, 74785. (Also, in some other cases it is not clear where the token starts, but that is the subject of another report I made) |
|
|
As stated in 0001082:0003406 we believe that the current wording is sufficiently clear and the use of the term is clearly stated in the previous paragraph. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-10-12 08:08 | Mark_Galeck | New Issue | |
| 2016-10-12 08:08 | Mark_Galeck | Name | => Mark Galeck |
| 2016-10-12 08:08 | Mark_Galeck | Section | => 2.3 Token Recognition |
| 2016-10-12 08:08 | Mark_Galeck | Page Number | => 2347-2348 |
| 2016-10-12 08:08 | Mark_Galeck | Line Number | => 74751-74792 |
| 2016-10-12 11:58 | kre | Note Added: 0003406 | |
| 2016-10-12 13:52 | Mark_Galeck | Note Added: 0003407 | |
| 2016-10-28 08:19 | geoffclare | Relationship added | related to 0001100 |
| 2018-04-12 15:36 | nick | Interp Status | => --- |
| 2018-04-12 15:36 | nick | Note Added: 0003951 | |
| 2018-04-12 15:36 | nick | Status | New => Closed |
| 2018-04-12 15:36 | nick | Resolution | Open => Rejected |
