Minutes of the 12 July 2012 Teleconference Austin-563 Page 1 of 1 Submitted by Eric Blake. 19 July, 2012 Attendees Mark Brown, IBM, TOG OR Don Cragun, PASC OR Joerg Schilling, Fraunhofer Society Nick Stoughton, USENIX, ISO/IEC OR Jim Pugsley, Oracle Eric Blake, Red Hat Apologies Geoff Clare, The Open Group Andrew Josey, The Open Group * Old Business +Bug 0000561: NUL-termination of sun_path in Unix sockets OPEN http://austingroupbugs.net/view.php?id=561 We agreed to leave this open as Eric plans to update the proposal. +mbsnrtowcs() discussion OPEN We agreed to leave this open as Nick plans to file a defect report. +Bug 0000573: Please add '+' to the portable filename character set OPEN http://austingroupbugs.net/view.php?id=573 Joerg has an action to prepare a proposed change. +Bug 0000576: No format specifiers for several types. OPEN http://austingroupbugs.net/view.php?id=576 There is still some discussion on the reflector on this item. Nick agree to raise the matter with the C committee. * Current Business Bug 0000584: Meaning of "minus sign" is not clear Accepted As Marked http://austingroupbugs.net/view.php?id=584 This item is tagged for TC2-2008 After the following changes are made, all existing occurrences of "minus-sign" and all but one appearance of "" should have been replaced by "". Note that the global changes below should be applied after all other changes have been applied to the draft. In the future, "minus-sign" should not appear in normative text and should not be used except in the one place left by this set of changes. The preferred term for future references to this glyph is . Note: The page and line numbers given below are from Base_TC1_Draft2.pdf. 
Change:
   "indicates either a  or minus-sign),"
to:
   "indicates either a  or ),"
on XBD Chapter 5 File Format Notation P123, L3436.

Change the characters in the Glyph column of Table 6-1 on P125,
L3505-3506 to be the same character.  (Note that the character used for
both of these should be the same character that is used in the construct
"('-')" in the rest of the standard.  This should not be done when that
construct appears in constant-width font, but I didn't find any case in
the TC1 draft where that happened.)

Change:
   " (’+’) character, or the minus-sign"
to:
   " (’+’) character, or the "
on XBD Clause 8.3 Other Environment Variables (TZ) P179, L5770.

Change:
   "minus-sign character (’−’)"
to:
   " character (’−’)"
on XSH strftime() DESCRIPTION P2022, L64567.

Change:
   "leading minus-sign for %F,"
to:
   "leading  for %F,"
on XSH strftime() RATIONALE P2029, L64850.

Change:
   "leading minus-sign (’−’) when using %Y"
to:
   "leading  (’−’) when using %Y"
on XSH strftime() RATIONALE P2029, L64858.

Change:
   "If the subject sequence begins with a minus-sign,"
to:
   "If the subject sequence begins with a ,"
on XSH strtod() DESCRIPTION P2051, L65528.

Change:
   "begins with a minus-sign,"
to:
   "begins with a ,"
on XSH strtol() DESCRIPTION P2059, L65823.

Change:
   "begins with a minus-sign,"
to:
   "begins with a ,"
on XSH strtuol() DESCRIPTION P2064, L65944.

Change:
   "minus-sign, the sequence shall be interpreted as negated."
to:
   ", the sequence shall be interpreted as negated."
on XSH wcstod() DESCRIPTION P2246, L71184.

Change:
   "minus-sign, the sequence shall be interpreted as negated."
to:
   ", the sequence shall be interpreted as negated."
on XSH wcstol() DESCRIPTION P2252, L71403.

Change:
   "minus-sign, the sequence shall be interpreted as negated."
to:
   ", the sequence shall be interpreted as negated."
on XSH wcstoul() DESCRIPTION P2259, L71565.

Change:
   "leading plus or minus sign"
to:
   "leading  or "
on XCU Section 2.6.4 Arithmetic Expansion on P2332, L74112.

Change:
   "sequence begins with a minus-sign,"
to:
   "sequence begins with a ,"
on XCU awk EXTENDED DESCRIPTION P2456, L78640.

Change:
   "A  (’+’) or a minus-sign (’−’)"
to:
   "A  (’+’) or a  (’−’)"
on XCU ex EXTENDED DESCRIPTION P2669, L86915.

Change:
   "preceded by a plus (’+’) or minus-sign (’−’) sign"
to:
   "preceded by a  (’+’) or  (’−’)"
on XCU awk OPERANDS P2762, L90490.

Change:
   "a minus-sign (’−’)."
to:
   "a  (’−’)."
on XCU ipcs STDOUT P2830, L92977.

Change:
   "A leading  or minus-sign shall be allowed."
to:
   "A leading  or  shall be allowed."
on XCU printf EXTENDED DESCRIPTION P3077, L102569.

Change:
   "optional minus-sign,"
to:
   "optional  character,"
on XCU sort OPTIONS P3211, L107574.

Change:
   "the character plus (’+’), the character minus (’−’), or digits),:
to:
   "the  (’+’), the  (’−’), or digits),"
in XRAT Section A.8.3 Other Environment Variables TZ rationale on P3499,
L118222.

Globally change all occurrences of "" except on P125, L3506 (in
Table 6-1 Portable Character Set) to "".
Bug 0000581: Grammar does not accept 'for i; do ...; done' Accepted, Interpretation Required http://austingroupbugs.net/view.php?id=581 This item is tagged for TC2-2008 Interpretation response ------------------------ The standard states that the shell grammar does not accept such usage, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: ------------- Since all existing implementations either accept the enhanced grammar, or have patches available to fix it, a future version of this standard should relax this constraint. In particular, David Korn, author and maintainer of the Korn Shell, says: From: David Korn Subject: Re: Austin Group bug 0000581: Grammar does not accept 'for i; do ...; done' Date: 29 June 2012 17:04:31 GMT+01:00 To: ajosey@opengroup.org Subject: Re: Austin Group bug 0000581: Grammar does not accept 'for i; do ...; done' -------- I have no objections. I have already made the change and it is in the beta version posted on our website. It was a one line change. David Korn dgk@research.att.com Notes to the Editor (not part of this interpretation): ------------------------------------------------------- Implement the change suggested in the Desired Action. in section 2.10.2 Shell Grammar Rules, change the for_clause in the indicated lines from for_clause : For name linebreak do_group | For name linebreak in sequential_sep do_group | For name linebreak in wordlist sequential_sep do_group ; to for_clause : For name do_group | For name sequential_sep do_group | For name linebreak in sequential_sep do_group | For name linebreak in wordlist sequential_sep do_group ; Bug 0000591: No reason for OH margins in the synopses of open and creat Accepted As Marked http://austingroupbugs.net/view.php?id=591 This item is tagged for TC2-2008 Solution 2 was agreed upon, as an editorial change: In XBD 1.7.1 Codes, change lines 266-270 from: #include #include struct group *getgrnam(const char *name); The OH margin legend indicates that the marked header is not required on XSI-conformant systems. to: #include #include int open(const char *path, int oflag, ...); The OH margin legend indicates that the optional header defines constants that will be needed if the function is called with certain flag arguments; thus it may be required for some of the functionality described, but is not needed otherwise. At each of the following SYNOPSIS locations: line 19444 (faccessat, via access) line 22157 (fchmodat, via chmod) line 22312 (fchownat, via chown) line 31644 (fstatat) line 32362 (utimensat, via futimens) line 40104 (linkat, via link) line 42301 (mkdirat, via mkdir) line 42498 (mkfifoat, via mkfifo) line 42617 (mknodat, via mknod) (also with XSI shading) line 55843 (readlinkat, via readlink) line 56920 (renameat, via rename) (also with CX shading) line 65046 (symlinkat, via symlink) line 68003 (unlinkat, via unlink) insert a line with OH shading: #include Also, at the following SEE ALSO locations: line 42393 (mkdir) line 42594 (mkfifo) line 42745 (mknod) line 55930 (readlink) line 57083 (rename) line 65140 (symlink) add a reference to . Bug 0000554: Five(?) clarifications of the informal regex descriptions Open http://austingroupbugs.net/view.php?id=554 The group began discussions on this bug, and agreed to address all 5 points in the scope of this bug rather than splitting into five reports. The bug was edited to make line numbers reflect the current standard, but it was agreed to leave it open for another week to come to consensus on the actual changes to make. Action: Eric to create a new bug for any further uses of OH margin marking for Issue 8 (see http://austingroupbugs.net/view.php?id=591#c1279) Next Steps ---------- The next call is on July 19 and will continue processing defect reports. Note that neither Andrew or Geoff will be on that call. In their absence Eric has agreed to take the minutes. This call will be for the regular 90 minutes. http://austingroupbugs.net See the calendar for the list of dialup numbers. An IRC channel will be available for the meeting irc://irc.freenode.org/austingroupbugs