Re: [1003.1(2016)/Issue7+TC2 0001105]: problems with backslashes in awk strings and EREs

Apparently, some are reading that as since the \55 is not encoded directly as a the user's intent was to treat it as a literal (or any character specified this way), not ERE operator, as another means of specifying '\-' in this case. An implementation that doesn't use regcomp may only permit

Minutes of the 3rd May 2018 Teleconference

All Enclosed are the minutes of yesterdays meeting regards Andrew -- Minutes of the 3rd May 2018 Teleconference Austin-866 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 4th May 2018 Attendees: Mark Ziegast, SHware Systems Dev. Joerg Schilling, FOKUS Fraunhofer Don

Austin Group teleconference +1-888-426-6840 PIN: 2115756

BEGIN:VCALENDAR VERSION:2.0 PRODID:-//opengroup.org//NONSGML kigkonsult.se iCalcreator 2.22.1// CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/New_York X-LIC-LOCATION:America/New_York BEGIN:DAYLIGHT TZOFFSETFROM:-0500 TZOFFSETTO:-0400 TZNAME:EDT DTSTART:20120311T02

Re: [1003.1(2016)/Issue7+TC2 0001105]: problems with backslashes in awk strings and EREs

Stephane Chazelas wrote, on 04 May 2018: > > 2018-05-04 09:30:56 +0100, Geoff Clare: > [...] > > > That's the point: we should allow \ to be an escaping operator > > > inside brackets. In awk and anything else. Technically, that > > > means a portable application has