Minutes of the 3 Feb 2011 Teleconference Austin-512 Page 1 of 1 Submitted by Andrew Josey, The Open Group. February 4 , 2011 Attendees Andrew Josey, The Open Group Don Cragun, PASC OR Geoff Clare, The Open Group Nick Stoughton, USENIX, ISO/IEC OR Eric Blake, Red Hat Jim Pugsley, Oracle Apologies: Geoff Clare, The Open Group Mark Brown, IBM, TOG OR We had some problems with the dialup line and used a temporary number for this call. Action: Andrew to contact Mark regarding the mastercode. *Old Business carried forward: TC1 PAR: Andrew noted we need to complete the PASC PMC criteria for the PAR. We will need to estimate a schedule for draft development. After email from Michael Kipness he now has information to draft a schedule. Action: Andrew Send draft PMC criteria to Austin Core (completed) Action: Send PMC criteria to SEC C1x Comments: Nick will file the comments he has received against the C standard today. * New Business * We picked up on regular Bug processing Bug 0000373: make should allow dash in macro names OPEN http://austingroupbugs.net/view.php?id=373 A note was added to this bug. Concerns were raised on the 3 Feb 2011 conference as to whether leading period, dash, or digits are portable; a further sentence may be needed to restrict macro names to start with a letter or underscore Bug 0000339: Add _SC_NPROCESSORS_CONF / _SC_NPROCESSORS_ONLN to sysconf(3) / unistd.h OPEN http://austingroupbugs.net/view.php?id=339 We revisited this item. It was agreed that Andrew should send a reminder to the originator (completed). Bug 0000162: Determining System Endianess during Preprocessing OPEN http://austingroupbugs.net/view.php?id=162 No paper was submitted, so this issue is not being progressed in C. Nick took an action to submit a proposal (completed) Add the following to XBD in the correct alphabetic location (after dlfcn.h, before errno.h): NAME endian.h - system endianness SYNOPSIS #include DESCRIPTION The header shall define at least the following symbolic constants for use in determining host byte order: BYTE_ORDER this macro shall have a value equal to one of the *_ENDIAN macros in this header. LITTLE_ENDIAN if BYTE_ORDER == LITTLE_ENDIAN, the host byte order is from least significant to most significant. BIG_ENDIAN if BYTE_ORDER == BIG_ENDIAN, the host byte order is from most significant to least significant. The macros BIG_ENDIAN and LITTLE_ENDIAN shall have distinct values. Implementations may define other macros with the _ENDIAN suffix. APPLICATION_USAGE None RATIONALE Many implementations also include PDP_ENDIAN to indicate a byte ordering where each pair of bytes is swapped. If BIG_ENDIAN is defined as 4321, PDP_ENDIAN would be 3412. However, this scheme is not universal, and derives its name from an obsolete processor. FUTURE DIRECTION None. SEE ALSO htons(), htonl(), ntohs(), ntohl(), swab() CHANGE HISTORY Added at Issue 8 Add to table on P471 after line 15969 Header Prefix Suffix Complete Name _ENDIAN We discussed bugs 243, 244, and 245 (Add -0 option to ....) No change to the status was made, although it was felt that we are heading towards a rejection with a cleaner solution being that the newline character should be disallowed in a filename. This is also the subject of another bug (bug 251 - which Don has an outstanding action on). Bug 0000374: malloc(0) and realloc(p,0) must not change errno on success http://austingroupbugs.net/view.php?id=374 OPEN Concerns were raised during the 3 Feb 2011 conference about line 56034 of realloc; is realloc(ptr, 0) allowed to return a non-NULL value, and therefore, should a NULL return when ptr is freed also need special treatment for whether errno is unchanged on success. This will require feedback from the C committee. Next Steps ---------- The next call will be on February 17th 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