Minutes of the 29th February 2024 Teleconference Austin-1389 Page 1 of 1 Submitted by Andrew Josey, The Open Group. 2nd March 2024 Attendees: Don Cragun, IEEE SA OR Mark Ziegast, SHware Systems Dev. (Happy Leap Day) Nick Stoughton, Logitech/USENIX, ISO/IEC JTC 1/SC 22 OR Eric Ackermann, CISPA Geoff Clare, The Open Group Eric Blake, Red Hat, The Open Group OR Apologies: Andrew Josey, The Open Group * General news There is no meeting on Monday 2024-03-04. * Current Business Bug 1804: still some minor clarifications in the sed RE description Accepted as Marked https://austingroupbugs.net/view.php?id=1804 This item is tagged for TC1-2024 At page 3356 lines 114143 - 114145 change: The escape sequence '\n' shall match a embedded in the pattern space. A literal shall not be used in the RE of a context address or in the substitute function. to: The escape sequence followed by an 'n' shall match a embedded in the pattern space. The application shall ensure that an escaped literal is not used in the RE of a context address or the RE of an s command. At page 3360 line 114308 - 114320 change: Replace all occurrences of characters in string1 with the corresponding characters in string2. If a followed by an 'n' appear in string1 or string2, the two characters shall be handled as a single . If (after resolving any escape sequences) the numbers of characters in string1 and string2 are not equal, or if any of the characters in string1 appear more than once, the results are undefined. Any character other than or can be used instead of to delimit the strings. If the delimiter is not 'n', within string1 and string2, the delimiter itself can be used as a literal character if it is preceded by an unescaped . If a character is escaped by an immediately preceding unescaped character in string1 or string2, the two characters shall be treated as a single literal character. The meaning of an unescaped followed by any character that is not 'n', a , or the delimiter character is undefined. to: Replace all occurrences of characters in string1 with the corresponding characters in string2. Any character other than or can be used instead of to delimit the strings. If the delimiter is not 'n', within string1 and string2, the delimiter itself can be used as a literal character if it is preceded by an unescaped . If a character is escaped by a preceding unescaped character in string1 or string2, the two characters shall represent a single literal character. If an 'n' character is escaped by a preceding unescaped character in string1 or string2, the two characters shall represent a single literal . The meaning of an unescaped followed by any character that is not 'n', a , or the delimiter character is undefined. If (after resolving any escape sequences) the numbers of characters in string1 and string2 are not equal, or if any of the characters in string1 appear more than once, the results are undefined. 1798: Must posix_getdents remember file offsets across exec? Accepted as Marked https://austingroupbugs.net/view.php?id=1798 This item is tagged for TC1-2024. An interpretation timer should start after approval of Issue 8. Proposed interpretation (review timer to start after approval of issue 8) ... Interpretation response: The standard states that the posix_getdents() function starts reading at the current file offset in the open file description associated with fildes, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: Elsewhere the standard makes allowances for implementations where directory streams are not implemented using a file descriptor, but this was not extended to the new posix_getdents() function when it was added. Notes to the Editor (not part of this interpretation): After page 920 line 31407 section fdopendir(), add a new paragraph: If the file descriptor specified by fd is associated with an open file description on which posix_getdents() has previously been used, the behavior is unspecified. After page 1567 line 52616 section posix_getdents(): The behavior is unspecified if lseek() is used to set the file offset to a value other than zero or a value returned by a previous call to lseek() on the same open file description. add these sentences: The behavior is unspecified if calls to posix_getdents() are made on different file descriptors that refer to the same open file description (for example, before and after a file descriptor is inherited across fork() or the exec family of functions, or is duplicated using dup() or fcntl()), unless lseek() is used to set the file offset to zero in between the calls to posix_getdents(). A single exception to this condition is that after a call to fork(), either the parent or child (but not both) can continue processing the directory using posix_getdents(); if both the parent and child processes use the function, the result is unspecified. Likewise, the behavior is unspecified if in between two calls to posix_getdents() on one file descriptor, the file offset is altered by a call made on a different file descriptor that refers to the same open file description and the new offset is not zero. After page 1571 line 52771 section posix_getdents(), add a new paragraph to RATIONALE: The restrictions on the use of different file descriptors that refer to the same open file description are needed in order to enable implementations where directory streams are not implemented using a file descriptor to maintain some internal state related to a particular file descriptor. At page 1858 line 61319 section readdir(), change: the result is undefined. to: the result is unspecified. 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. Next Steps ---------- The next call is on: Mon 2024-03-04 NO meeting Thu 2024-03-07 (Zoom meeting - general bugs) Mon 2024-03-11 (Zoom meeting - general bugs) 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)