Minutes of the 6th September 2018 Teleconference     Austin-884 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 8th September 2018

Attendees:

    Mark Ziegast, SHware Systems Dev.
    Joerg Schillng, FOKUS Fraunhofer
    Don Cragun ,IEEE PASC OR
    Nick Stoughton, USENIX, ISO/IEC JTC 1/SC 22 OR
    Geoff Clare, The Open Group
    Martin Rehak, Oracle, The Open Group OR
    Andrew Josey, The Open Group (partial)
    Eric Blake, Red Hat
    Drew DeVault, independent, just listening (and does not have a microphone)

Apologies:
  David Clissold, IBM

* General news 

A quick update on the status of the pipefail discussion from the mailing list.
A question of whether David Korn is still reachable, rumour has it that he
has now retired.

Eric raised a request from MUSL libc for us to review bug id 900 (qsort_r) on a future call.

* 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 9 March 2018 and earlier)

* Current Business

Bug 1077: Recommend support for wide-character regcomp and regexec and/or specify multi-byte behavior OPEN
http://austingroupbugs.net/bug_view_page.php?bug_id=1077

Andrew has completed the action to ping his Apple contact and is
awaiting a reply.

Bug 1122: POSIX should include gettext() and friends  OPEN
http://austingroupbugs.net/view.php?id=1122

Left open as an action is still in progress to flesh out a complete proposal.



Bug 1130: Address 0 does not make sense for the c command Accepted as Marked
http://austingroupbugs.net/view.php?id=1130

This item is tagged for TC3-2008

Suggested change: On page 2682, line 87448, delete "Address 0 shall
be valid for this command; it shall be interpreted as if address 1
were specified."

On page 2691, lines 87803-87805, change from:
   For consistency with the a and r commands and better user
   functionality, the i and c commands must also accept an address
   of 0, in which case 0i is treated as 1i and likewise for the c
   command.
to:

    For consistency with the a and r commands and better user
    functionality, the i command also accepts an address of 0.
    However, it is unspecified if <tt>0i</tt> is treated as <tt>1i</tt>
    (which will fail if the buffer is empty), or means insert at
    the beginning of the buffer (which will succeed even if the
    buffer is empty). Earlier versions of this standard required
    address 0 for the c command to be treated as 1 also, but this
    requirement has been removed, though implementations are permitted
    to do this as an extension.


Bug 1131: The synopsis of the i command is wrong and inconsistent with the synopsis of the a command Accepted as marked.
http://austingroupbugs.net/view.php?id=1131

This bug is tagged for TC3-2008.

On page 2684 line 87533 section ed, change:
    Address 0 shall be valid for this command; it shall be interpreted
    as if address 1 were specified.
to:
    Address 0 shall be valid for this command; it is unspecified
    whether it causes the inserted text to be placed at the beginning
    of the buffer or it is interpreted as if address 1 were specified.
    (These two allowed behaviors differ in the case that the buffer
    is empty.)


Next Steps
----------
The next call is on Sep 13th 2018 (Thursday).

Apologies in Advance:
  Nick Stoughton (2018-09-20)
  Andrew Josey (tentative 2018-09-13)

Calls are anchored on US time. (8am Pacific) 
This call will be for the regular 90 minutes.

http://austingroupbugs.net

An etherpad is usually up for the meeting, with a URL using the date format as below:

https://posix.rhansen.org/p/201x-mm-dd
username=posix password=2115756#