View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001552 | 1003.1(2016/18)/Issue7+TC2 | Shell and Utilities | public | 2022-01-14 23:55 | 2022-01-18 00:34 |
Reporter | calestyo | Assigned To | |||
Priority | normal | Severity | Editorial | Type | Enhancement Request |
Status | Closed | Resolution | Duplicate | ||
Name | Christoph Anton Mitterer | ||||
Organization | |||||
User Reference | |||||
Section | 2.13.1 Patterns Matching a Single Character | ||||
Page Number | - | ||||
Line Number | - | ||||
Interp Status | --- | ||||
Final Accepted Text | |||||
Summary | 0001552: minor improvement in the description of […] in pattern matching notation | ||||
Description | Right now the text says: "If an open bracket introduces a bracket expression as in XBD RE Bracket Expression, except that the <exclamation-mark> character ( '!' ) shall replace the <circumflex> character ( '^' ) in its role in a non-matching list in the regular expression notation, it shall introduce a pattern bracket expression. A bracket expression starting with an unquoted <circumflex> character produces unspecified results. Otherwise, '[' shall match the character itself." | ||||
Desired Action | I would propose to swap the last two sentences, i.e. first: "Otherwise, '[' shall match the character itself." followed by "A bracket expression starting with an unquoted <circumflex> character produces unspecified results." Otherwise the meaning could be interpreted, that a [ would match itself, if the bracket expression was not starting with an unquoted ^ . Whereas that sentence rather relates to the 1st sentence, i.e. "If an open bracket introduces a bracket expression..." and ONLY if it does NOT result into a bracket expression, it (the [ ) shall be taken literally. Cheers, Chris. | ||||
Tags | No tags attached. |
duplicate of | 0000985 | Closed | 1003.1(2013)/Issue7+TC1 | quote removal missing from case statement patterns and alternative expansions |
|
This problem has already been fixed by bug 0000985. This bug should be closed as a dup of 985. |
|
Formulation there seems fine and solve the issue from here as well. So I agree that this should be closed. |
|
Closed as requested by submitter. |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-01-14 23:55 | calestyo | New Issue | |
2022-01-14 23:55 | calestyo | Name | => Christoph Anton Mitterer |
2022-01-14 23:55 | calestyo | Section | => 2.13.1 Patterns Matching a Single Character |
2022-01-14 23:55 | calestyo | Page Number | => - |
2022-01-14 23:55 | calestyo | Line Number | => - |
2022-01-17 10:33 | geoffclare | Note Added: 0005615 | |
2022-01-17 10:34 | geoffclare | Relationship added | duplicate of 0000985 |
2022-01-17 18:49 | calestyo | Note Added: 0005619 | |
2022-01-18 00:34 | Don Cragun | Interp Status | => --- |
2022-01-18 00:34 | Don Cragun | Note Added: 0005620 | |
2022-01-18 00:34 | Don Cragun | Status | New => Closed |
2022-01-18 00:34 | Don Cragun | Resolution | Open => Duplicate |