Minutes of the 11th February 2019 Teleconference     Austin-908 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 12th February 2019

Attendees:
    Don Cragun, IEEE PASC OR
    Mark Ziegast, SHware Systems Dev.
    Geoff Clare, The Open Group
    Eric Blake, Red Hat
    Andrew Josey, The Open Group 

* General news 

Andrew noted on his action to check in with Martin Rehak on
participation, that this is open, awaiting further feedback from
Oracle.

* 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)

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.


* Current Business

Bug 1055: unspecified how much is parsed before execution begins   Accepted as Marked
http://austingroupbugs.net/view.php?id=1055

This item is tagged for TC3-2008

On (2016 edition) page 2348 after line 74792 (just before XCU 2.3.1
Alias Substitution), insert a new paragraph:
    In situations where the shell parses its input as a program,
    once a complete_command has been recognized by the grammar (see
    [xref to 2.10 Shell Grammar]), the complete_command shall be
    executed before the next complete_command is tokenized and
    parsed.

After (2016 edition) page 2412 line 77241 (set Application Usage),
add a new paragraph:
    Use of <tt>set -n</tt> causes the shell to parse the rest of
    the script without executing any commands, meaning that <tt>set
    +n</tt> cannot be used to undo the effect. Syntax checking is
    more commonly done via <tt>sh -n script_name</tt>.

After (2016 edition) page 3239 line 108855 (sh utility Application
Usage), add a new paragraph:
    <tt>sh -n</tt> can be used to check for many syntax errors
    without waiting for complete_commands to be executed, but may
    be fooled into declaring false positives or missing actual
    errors that would occur when the shell actually evaluates eval
    commands present in the script, or if there are alias (or
    unalias) commands in the script that would alter the syntax of
    commands that use the affected aliases.

On (2016 edition) page 3720 after line 127520 (just before XRAT
C.2.3.1), insert a new paragraph:
    Because a complete_command encountered during a program is
    executed before the next complete_command is tokenized and
    parsed, syntax errors are not discovered by the shell until
    just before the code would be executed. While in some cases it
    might be desirable to detect and react to syntax errors before
    anything is executed (possible with <tt>sh -n</tt>), deferring
    the discovery of syntax errors has several benefits:

	It makes it possible for script authors to test for the
	availability of a nonstandard extension and react appropriately
	before the use of the extension would trigger a syntax
	error.

	It makes it possible to create self-extracting tarballs (a
	shell script concatenated with a payload archive that
	extracts the archive when executed).

	The shell does not have to read and parse the complete
	script before execution, which reduces memory usage when
	executing extremely long scripts.

Next Steps 
----------

The next calls are on:

February 14th 2019 (Thursday)
This call will be for 90 minutes.

February 18th 2019 (Monday). 
This call will be for 60 minutes.

Apologies in advance:
   2019-02-14 Mark Ziegast

Calls are anchored on US time. (8am Pacific) 

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#