Minutes of the 16th February 2017 Teleconference Austin-802 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 17th February 2017 Attendees: David Clissold, IBM Don Cragun, IEEE PASC OR Joerg Schilling, FOKUS Fraunhofer Eric Blake, Red Hat Mark Ziegast, SHware Systems Geoff Clare, The Open Group Andrew Josey, The Open Group Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Apologies Richard Hansen, Google Martin Rehak, Oracle, The Open Group OR * General news We discussed 2038 (the 32 bit time rollover). We also discussed about the PAR and whether we can do a rollup to the standard, and still have a normative reference to C99. If not, then it might take us two years to align with C11. Andrew has an action to contact IEEE for feedback. * Outstanding actions ( Please note that this section has been flushed to shorten the minutes - to locate the previous set of outstanding actions, look to the minutes from 28 Jan 2016) Bug 0000249: Add standard support for $'...' in shell Reopened http://austingroupbugs.net/bug_view_page.php?bug_id=249 We will return to bug 249 on a future call. Bug 0000953: Alias expansion is under-specified Was Accepted as Marked http://austingroupbugs.net/view.php?id=953 Richard has an action to propose new wording to discuss in a future telecon. * Current Business Bug #1031: Add -iname (case-insensitive name search) to the find utility. Accepted as marked. http://austingroupbugs.net/view.php?id=1031 This item is tagged for Issue 8. (2016 edition page and line numbers) On page 107 before line 2926 (XBD chapter 4 General Concepts), insert a new section: 4.1 Case Insensitive Comparisons When a standard utility or function that uses regular expressions or pattern matching specifies that matching shall be case insensitive, then if a string would match the regular expression or pattern when doing a case-sensitive match, the same string with any of its characters replaced with their case counterparts, as defined by the toupper and tolower character mappings (see [xref to XBD 7.3.1]), shall also match when doing a case-insensitive match. This definition of case-insensitive processing is intended to allow matching of multi-character collating elements as well as characters, as each character in the string is matched using both its cases. For example, in a locale with a "Ch" multi-character collating element (see [xref to XBD 7.3.2 bullet 1]), the bracket expression "[[.Ch.]]" (see [xref to XBD 9.3.5 bullet 4]) matches the strings "ch", "Ch", "cH", and "CH" when matching without regard to case. and renumber the following sections. On page 182 line 6030 (XBD 9.2) change: When a standard utility or function that uses regular expressions specifies that pattern matching shall be performed without regard to the case (uppercase or lowercase) of either data or patterns, then when each character in the string is matched against the pattern, not only the character, but also its case counterpart (if any), shall be matched. This definition of case-insensitive processing is intended to allow matching of multi-character collating elements as well as characters, as each character in the string is matched using both its cases. For example, in a locale where "Ch" is a multi-character collating element and where a matching list expression matches such elements, the RE "[[.Ch.]]" when matched against the string "char" is in reality matched against "ch", "Ch", "cH", and "CH". to: Some standard utilities and functions support case-insensitive regular expression matching. When this type of matching is in effect, the matching process shall be modified as described in [xref to XBD 4.1]. On page 2797 after line 91930 (XCU section find operands) add a new item: -iname pattern The -iname primary shall be equivalent to -name, except that the match shall be case insensitive. See [xref to XBD 4.1]. On page 2800 line 92074 (XCU section find (LC_COLLATE)), change: used in the pattern matching notation for the -n option to: used in the pattern matching notation for the -name, -iname and -path primaries On page 2800 line 92079 (XCU section find (LC_CTYPE)), change: within the pattern matching notation used for the -n option to: within the pattern matching notation used for the -name, -iname and -path primaries On page 2843 line 93633 (XCU section grep), change: Perform pattern matching in searches without regard to case; to: Perform pattern matching in a case-insensitive manner; On page 3005 line 99882 (XCU more), change: Perform pattern matching in searches without regard to case; to: Perform pattern matching in a case-insensitive manner; Cross-volume changes to XBD ... On page 254 after line 8520 (XBD section ), add the following new items: FNM_CASEFOLD string and pattern are compared in a case-insensitive manner. See [xref to XBD 4.1]. FNM_IGNORECASE Equivalent to FNM_CASEFOLD. On page 323 line 10972 (XBD section ), change: Ignore case in match to: Perform pattern matching in a case-insensitive manner Cross-volume changes to XSH ... On page 890 after line 30073 (XSH section fnmatch()), add a new paragraph: If FNM_CASEFOLD or FNM_IGNORECASE is set, string and pattern shall be compared in a case-insensitive manner. See [xref to XBD 4.1]. On page 1802 line 58345 (XSH section regcomp()), change: Ignore case in match (see [xref to XBD Chapter 9]) to: Perform matching in a case-insensitive manner (see [xref to XBD 9.2]) Cross-volume changes to XRAT ... On page 3511 line 118810 (XRAT A.4), insert a new section: A.4.1 Case Insensitive Comparisons Case-insensitive matching is defined in this standard in terms of a simple algorithm whereby, for each character in the string to be matched, if the character is uppercase then the lowercase equivalent (if any) is also checked for a match, and if the character is lowercase then the uppercase equivalent (if any) is also checked for a match. It is described this way to make the expected behavior easier to understand; however, implementations may internally use more sophisticated algorithms to improve efficiency, provided that the result is the same as the simple algorithm would produce. and renumber the following A.4.x sections. Bug 0001033: LOG_UPTO(): Present on all (?) systems, but not standardized? OPEN http://austingroupbugs.net/view.php?id=1033 We started on this bug and will continue next week. Next Steps ---------- The next call is on February 23rd, 2017 (a Thursday) Calls are anchored on US time. (8am Pacific) This call will be for the regular 90 minutes. http://austingroupbugs.net An IRC channel will be available for the meeting irc://irc.freenode.net/austingroupbugs An etherpad is usually up for the meeting, with a URL using the date format as below: http://posix@posix.rhansen.org:9001/p/201x-mm-dd password=2115756#