On 9/2/16 10:46 AM, Herbert Xu wrote: > On Fri, Sep 02, 2016 at 09:25:15AM -0500, Eric Blake wrote: >> >> 2.13.1 Patterns Matching a Single Character >> >> [ >> 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. > > BTW, this last sentence is not present in > > http://pubs.opengroup.org/onlinepubs/009604499/utilities/xcu_chap02.html#tag_02_13 That's pretty old; it's from 2004. > So I presume it's a newer unreleased revision. It's in the current revision, which dates from 2008. > > Seriously, you guys are turning POSIX into a joke by introducing > all these new requirements. At this point I think we should > pretty much give up on POSIX compliance the way it's headed. Let's not go overboard here. This was introduced to tighten up ambiguous behavior: what happens when the open bracket *doesn't* introduce a bracket expression. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@xxxxxxxx http://cnswww.cns.cwru.edu/~chet/ -- To unsubscribe from this list: send the line "unsubscribe dash" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html