View Issue Details

IDProjectCategoryView StatusLast Update
00012771003.1(2016/18)/Issue7+TC2Shell and Utilitiespublic2024-06-11 09:08
Reportergeoffclare Assigned To 
PrioritynormalSeverityEditorialTypeError
Status ClosedResolutionAccepted 
NameGeoff Clare
OrganizationThe Open Group
User Reference
Sectionawk
Page Number2491
Line Number80131
Interp Status---
Final Accepted Text
Summary0001277: Use of <slash> in an ERE in awk
DescriptionThe 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 ActionChange:
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.
Tagstc3-2008

Relationships

related to 0001105 Closed problems with backslashes in awk strings and EREs 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-07-31 14:33 geoffclare New Issue
2019-07-31 14:33 geoffclare Name => Geoff Clare
2019-07-31 14:33 geoffclare Organization => The Open Group
2019-07-31 14:33 geoffclare Section => awk
2019-07-31 14:33 geoffclare Page Number => 2491
2019-07-31 14:33 geoffclare Line Number => 80131
2019-07-31 14:33 geoffclare Interp Status => ---
2019-07-31 14:34 geoffclare Relationship added related to 0001105
2019-08-22 15:39 Don Cragun Status New => Resolved
2019-08-22 15:39 Don Cragun Resolution Open => Accepted
2019-08-22 15:40 Don Cragun Tag Attached: tc3-2008
2019-11-20 16:17 geoffclare Status Resolved => Applied
2024-06-11 09:08 agadmin Status Applied => Closed