Stephane CHAZELAS <[email protected]> wrote, on 03 May 2018: > > 2018-05-03 15:54:58 +0000, Austin Group Bug Tracker: > [...] > > On page 2492 line 80144 section awk, add two new rows to the table:<pre> > > \., \[, \(, \*, \+, | A <backslash> character followed by a character | In > > the lexical token <b>ERE</b>, the sequence > > \?, \{, \|, \^, \$ | that has a special meaning in EREs (see | > > shall represent itself. Otherwise undefined. > > | [xref to XBD 9.4.3]), other than <backslash>. | > > --------------------+-------------------------------------------------+----------------------------------------------------- > > \\ | Two <backslash> characters. | In > > the lexical token <b>ERE</b>, the sequence shall > > | | > > represent itself. In the lexical token <b>STRING</b>, > > | | it > > shall represent a single <backslash>. > > </pre> > [...] > > Thanks. > > Does that mean that: > > awk '/[\]]/' > > is to match on "\]" and not on "]" (like for grep -E '[\]]')?
As things stand, since "\]" is not in the table above, it is covered by the "\c" catchall (last row of the table) which says the behaviour is undefined. -- Geoff Clare <[email protected]> The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX, England
