Minutes of the 3rd November 2011 Teleconference Austin-540 Page 1 of 1 Submitted by Andrew Josey, The Open Group. November 7 , 2011 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Mark Brown, IBM, TOG OR Jim Pugsley, Oracle Geoff Clare, The Open Group Nick Stoughton, USENIX, ISO/IEC OR Eric Blake, Red Hat The TC1-2008 Draft 4 document is still progressing. Andrew has sent a note to IEEE confirming that we want to let the PAR for 1003.27 (C++) be withdrawn due to lack of progress. * New Business Bug 0000500: Special meaning of inside double quotes Accepted as marked http://austingroupbugs.net/view.php?id=500 An interpretaion is required. This item is tagged for Issue 8 Interpretation response The standard is unclear on this issue, and no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor, with a suggested set of corrections in Note: 0000998 . Notes to the Editor (not part of this interpretation): If approved, please use the corrective wording supplied in Note: 0000998 (note 998 included below) Note that 0000221 makes extensive changes to the paragraph at page 2299 line 72382, hence the changes below do not need to cover the behaviour of backslash and double-quote within "${...}". On page 2298 line 72363 section 2.2.1 change: If a follows the to: If a immediately follows the On page 2299 line 72396-72398 section 2.2.3 change: The shall retain its special meaning as an escape character (see Section 2.2.1, on page 2298) only when followed by one of the following characters when considered special: $ ` " \ to: Outside of "$(...)" and "${...}" the shall retain its special meaning as an escape character (see Section 2.2.1, on page 2298) only when immediately followed by one of the following characters: $ ` \ or by a double-quote character that would otherwise be considered special (see Section 2.6.4 on page NNNN and Section 2.7.4 on page NNNN). On page 2299 line 72399 section 2.2.3 change: The application shall ensure that a double-quote is preceded by a to be included within double-quotes. to: The application shall ensure that a double-quote that is not within "$(...)" nor within "${...}" is immediately preceded by a in order to be included within double-quotes. Bug 0000465: is the list of special built-ins exhaustive (is "local" special)? OPEN http://austingroupbugs.net/view.php?id=465 Action: Andrew to send a reminder to Jonathan Nieder about his action Bug 0000375: Extend test/[...] conditionals: ==, <, >, -nt, -ot, -ef OPEN http://austingroupbugs.net/view.php?id=375 Action: Andrew to send a reminder to David Wheeler about his action Bug 0000374: malloc(0) and realloc(p,0) must not change errno on success OPEN http://austingroupbugs.net/view.php?id=374 This was further discussed at the Washington DC meeting of WG14, and C defect report 400 has been accepted. This will not be resolved for at least another 2 meetings - i.e. at least one year. This bug should remain open in the meantime. Bug 0000373: make should allow dash in macro names OPEN http://austingroupbugs.net/view.php?id=373 Eric has agreed to take an action to investigate the behavior on a number of platforms and report back. Bug 0000339: Add _SC_NPROCESSORS_CONF / _SC_NPROCESSORS_ONLN to sysconf(3) / unistd.h OPEN http://austingroupbugs.net/view.php?id=339 Action: Andrew to remind Garrett Cooper of his action Bug 0000337: Add standard support for "!=" (macro shell assignment) in make OPEN http://austingroupbugs.net/view.php?id=337 This item is dependent on bug 330. Bug 0000332: Add automatic remaking of makefiles Rejected http://austingroupbugs.net/view.php?id=332 In the 2011-11-03 teleconference it was agreed to close this bug as there is no consensus to make the requested change. Bug 0000330: In make, add support for assignments ":=", "+=", and "?=". OPEN http://austingroupbugs.net/view.php?id=330 A long discussion was held on this bug report. Bugnote 577 has attempted to address the differences between GNU and BSD makes, however the email discussion indicates this would be unlikely to pass a ballot. We are open to a new proposal. Next Steps ---------- The next call is on November 10th at 08:00 Pacific and will continue processing defect reports. 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.freestandards.org #austin ICAL: http://www.google.com/calendar/ical/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic XML: http://www.google.com/calendar/feeds/nvctqtstkuni3fab9k3jqtrt4g@group.calendar.google.com/public/basic