|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0000568 |
[1003.1(2008)/Issue 7] Shell and Utilities |
Objection |
Error |
2012-05-26 00:59 |
2019-06-10 08:55 |
|
|
Reporter |
Don Cragun |
View Status |
public |
|
|
Assigned To |
ajosey |
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Closed |
|
|
|
|
|
Name |
Don Cragun |
|
Organization |
Self |
|
User Reference |
|
|
Section |
2.3 Token Recognition |
|
Page Number |
2299 |
|
Line Number |
72419-72424 |
|
Interp Status |
--- |
|
Final Accepted Text |
|
|
|
Summary |
0000568: "current characters" should be "previous characters" in rules 2 and 3 |
|
Description |
As noted by Jens Schweikhardt in the main mailing list (sequence #17549), the use of "current characters" in rule 2 in XCU section 2.3 (Token Recognition): "If the previous character was used as part of an operator and the current character is not
quoted and can be used with the current characters to form an operator, it shall be used as
part of that (operator) token." is confusing because there is only one current character, and using a character with itself makes no sense.
As noted by David Korn's response, the "current characters" should be "previous characters".
The exact same problem appears in rule 3. |
|
Desired Action |
Change "current characters" in rule 2 on P2299, L72420 to "previous characters".
Change "current characters" in rule 3 on P2299, L72423 to "previous characters". |
| Tags |
tc2-2008 |
|
|
Attached Files |
|
|
|
Relationships 
