Re: [1003.1(2016)/Issue7+TC2 0001234]: in most shells, backslash doesn't have two meaning wrt pattern matching

On 23/09/2019 16:39, Austin Group Bug Tracker wrote: -- (0004564) geoffclare (manager) - 2019-09-23 15:39 http://austingroupbugs.net/view.php?id=1234#c4564

[1003.1(2016)/Issue7+TC2 0001289]: netdb.h - in_port_t and in_addr_t do not appear to be needed

A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1289 == Reported By:joelsherrill Assigned To:

[1003.1(2016)/Issue7+TC2 0001293]: Add methods associated with manipulating pthread affinity on SMP systems

The following issue has been SUBMITTED. == http://austingroupbugs.net/view.php?id=1293 == Reported By:joelsherrill Assigned To:

[1003.1(2016)/Issue7+TC2 0001291]: Add method to obtain pthread attributes

The following issue has been SUBMITTED. == http://austingroupbugs.net/view.php?id=1291 == Reported By:joelsherrill Assigned To:

[1003.1(2016)/Issue7+TC2 0001292]: Add pthread_setname, pthread_getname

The following issue has been SUBMITTED. == http://austingroupbugs.net/view.php?id=1292 == Reported By:joelsherrill Assigned To:

[1003.1(2016)/Issue7+TC2 0001290]: arpa/inet.h - origin of socklen_t is unclear

The following issue has been SUBMITTED. == http://austingroupbugs.net/view.php?id=1290 == Reported By:joelsherrill Assigned To:

[1003.1(2016)/Issue7+TC2 0001289]: netdb.h - in_port_t and in_addr_t do not appear to be needed

The following issue has been SUBMITTED. == http://austingroupbugs.net/view.php?id=1289 == Reported By:joelsherrill Assigned To:

Draft minutes of the 26 September 2019 Teleconference

These are the draft minutes from yesterday's call. Andrew will need to allocate the Austin-xxx document number and add the file to the document register after he returns. Regards, Geoff. --- Minutes of the 26 September 2019 Teleconference Austin-xxx Page 1 of 1 Submitted by Geoff

Re: More issues with pattern matching

"Schwarz, Konrad" wrote: > > -Original Message- > > From: Robert Elz > > > So, is [[:"alpha":]] required to be treated the same as [[:alpha:]] , not > > allowed to be treated the same, > > explicitly unspecified, or simply never considered (previously) ? > > An argument for requiring

Re: More issues with pattern matching

Robert Elz wrote, on 27 Sep 2019: > > | In the case of [x[:bogus:]], the use of both colons clearly indicates > | the intention to use the new character-class feature. If the name > | between the colons is not a valid class name, that is likely due to > | an error on the user or