Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
0001277 |
[1003.1(2016/18)/Issue7+TC2] Shell and Utilities |
Editorial |
Error |
2019-07-31 14:33 |
2019-11-20 16:17 |
|
Reporter |
geoffclare |
View Status |
public |
|
Assigned To |
|
Priority |
normal |
Resolution |
Accepted |
|
Status |
Applied |
|
|
|
|
Name |
Geoff Clare |
Organization |
The Open Group |
User Reference |
|
Section |
awk |
Page Number |
2491 |
Line Number |
80131 |
Interp Status |
--- |
Final Accepted Text |
|
|
Summary |
0001277: Use of <slash> in an ERE in awk |
Description |
The standard says:
Using a <slash> character within an ERE requires the escaping
shown in the following table.
but this is only true when the ERE is in the lexical token ERE.
In an ERE in a string, the opposite is true: escaping must not be used.
(The resolution of bug 0001105 clarifies this by making the meaning
of <backslash><slash> in an ERE in a string undefined.) |
Desired Action |
Change:Using a <slash> character within an ERE requires the escaping shown in the following table. to:Using a <slash> character within the lexical token ERE (except as one of the two delimiters) requires the escaping shown in the following table. |
Tags |
tc3-2008 |
|
Attached Files |
|
|