Minutes of the 13th May 2024 Teleconference Austin-1405 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 15th May 2024 Attendees: Andrew Josey, The Open Group Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR Don Cragun, IEEE SA OR Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Eric Ackermann, CISPA Brooks Harris Apologies Tom Thompson, IEEE Mark Ziegast, SHware Systems Dev * General news There will be no meeting on Monday May 27. The general news is unchanged. The IEEE Revcom committee met on May 6 to consider approval of draft 4.1. We have yet to hear the result. After approval we can moved forward to complete the frontmatter and proceed to publication, and the html conversion. The ISO/IEC ballot closes on June 28. * Current Business 1797: strftime "%s" should be able to examine tm_gmtoff OPEN https://austingroupbugs.net/bug_view_page.php?bug_id=1797 We will continue this item next time that Paul is available (expected in April). Bug 1818: Add strcasestr() & strcasestr_l() OPEN https://austingroupbugs.net/view.php?id=1818 Action: Eric B to ask The Open Group if they are willing to sponsor these functions for Issue 9. Bug 1820: The impact of changing NF should be stated Accepted as Marked https://austingroupbugs.net/view.php?id=1820 This item is tagged for Issue 9. On Issue 8 draft 4.1 page 2613 line 85507, change: Field variables shall be designated by a '$' followed by a number or numerical expression. The effect of the field number expression evaluating to anything other than a non-negative integer is unspecified; uninitialized variables or string values need not be converted to numeric values in this context. New field variables can be created by assigning a value to them. References to nonexistent fields (that is, fields after $NF), shall evaluate to the uninitialized value. Such references shall not create new fields. However, assigning to a nonexistent field (for example, $(NF+2)=5) shall increase the value of NF; create any intervening fields with the uninitialized value; and cause the value of $0 to be recomputed, with the fields being separated by the value of OFS. Each field variable shall have a string value or an uninitialized value when created. Field variables shall have the uninitialized value when created from $0 using FS and the variable does not contain any characters. If appropriate, the field variable shall be considered a numeric string (see Expressions in awk, on page 2608). to: Field variables shall be designated by a '$' followed by a number or numerical expression. The effect of the field number expression evaluating to anything other than a non-negative integer is unspecified; uninitialized variables or string values need not be converted to numeric values in this context. Each field variable shall have a string value or an uninitialized value when created. Field variables shall have the uninitialized value when created from $0 using FS and the variable does not contain any characters. If appropriate, the field variable shall be considered a numeric string (see Expressions in awk, on page 2608). New field variables can be created by assigning a value to them. References to nonexistent fields (that is, fields after $NF), shall evaluate to the uninitialized value. Such references shall not create new fields. However, assigning to a nonexistent field (for example, $(NF+2)=5) shall increase the value of NF; create any intervening fields with the uninitialized value; and cause the value of $0 to be recomputed, with the fields being separated by the value of OFS. Directly increasing the value of NF (for example, NF += 2) shall have the same effect as assigning an empty string to $NF (where NF has its new value). Decreasing the value of NF to a non-negative value shall remove all fields after $NF and cause the value of $0 to be recomputed, with the fields being separated by the value of OFS. Assigning to NF without changing its value (for example, NF = NF) shall cause the value of $0 to be recomputed, with the fields being separated by the value of OFS. Bug 1821: Define the values of $0, $1, etc. in the END section OPEN https://austingroupbugs.net/view.php?id=1821 We started on this item. Notes are in the etherpad. We will continue on this item next time. Next Steps ---------- The next call is on: Thu 2024-05-16 (WEBEX meeting - general bugs) Mon 2024-05-20 (WEBEX meeting - general bugs) Mon 2024-05-27 No meeting The calls are for 90 minutes Calls are anchored on US time. (8am Pacific) Please check the calendar invites for dial in details. Bugs are at: https://austingroupbugs.net An etherpad is usually up for the meeting, with a URL using the date format as below: https://posix.rhansen.org/p/20xx-mm-dd (For write access this uses The Open Group single sign on, for those individuals with gitlab.opengroup.org accounts. Please contact Andrew if you need to be setup)