From rinehuls@access.digex.net Mon Aug 3 23:31:54 1998 Received: from access1.digex.net (qlrhmEbBUV1EY@access1.digex.net [205.197.245.192]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id XAA12898 for ; Mon, 3 Aug 1998 23:31:50 +0200 Received: from localhost (rinehuls@localhost) by access1.digex.net (8.8.4/8.8.4) with SMTP id RAA13750 for ; Mon, 3 Aug 1998 17:31:46 -0400 (EDT) Date: Mon, 3 Aug 1998 17:31:46 -0400 (EDT) From: "william c. rinehuls" To: sc22docs@dkuug.dk Subject: SC22 N2781 - Summary of Voting on IS 9945-1, PDAM7 - POSIX Advanced , Realtime Extensions (C Language) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII _____________________ beginning of title page _______________________ ISO/IEC JTC 1/SC22 Programming languages, their environments and system software interfaces Secretariat: U.S.A. (ANSI) ISO/IEC JTC 1/SC22 N2781 TITLE: Summary of Voting on PDAM Approval for PDAM7 to IS 9945-1: Information technology - Portable Operating System Interface (POSIX) - Part 1: System Application Program Interface (API) - Amendment 7: Advanced Realtime Extensions (C Language) DATE ASSIGNED: 1998-08-03 SOURCE: Secretariat, ISO/IEC JTC 1/SC22 BACKWARD POINTER: N/A DOCUMENT TYPE: Summary of Voting PROJECT NUMBER: JTC 1.22.21.04.01.01 STATUS: WG15 is requested to prepare a Disposition of Comments Report and make a recommendation on the further processing of the PDAM. ACTION IDENTIFIER: FYI to SC22 Member Bodies ACT to WG15 DUE DATE: N/A DISTRIBUTION: Text CROSS REFERENCE: SC22 N2678 DISTRIBUTION FORM: Def Address reply to: ISO/IEC JTC 1/SC22 Secretariat William C. Rinehuls 8457 Rushing Creek Court Springfield, VA 22153 USA Telephone: +1 (703) 912-9680 Fax: +1 (703) 912-2973 email: rinehuls@access.digex.net __________ end of title page; beginning of overall summary ____________ SUMMARY OF VOTING ON Letter Ballot Reference: SC22 N2678 Issued by: JTC 1/SC22 Circulation Date: 1998-04-07 Closing Date: 1998-07-24 SUBJECT: PDAM Approval for PDAM7 to IS 9945-1: Information technology - Portable Operating System Interface (POSIX) - Part 1: System Application Program Interface (API) - Amendment 7: Advanced Realtime Extensions (C Language) ----------------------------------------------------------------------- The following responses have been received on the subject of approval: "P" Members supporting approval without comment 11 "P" Members supporting approval with comments 3 "P" Members not supporting approval 2 "P" Members abstaining 1 "P" Members not voting 5 "O" Members supporting approval without comments 1 "O" Members abstaining 1 ------------------------------------------------------------------------- Secretariat Action: WG15 is requested to prepare a Disposition of Comments Report and make a recommendation on the further processing of the PDAM. The comment accompanying the abstention vote from France was: "Due to lack of resources." The comment accompanying the abstention vote from Sweden was: "Due to lack of expertise." The comment accompanying the affirmative vote from Canada was: "We recommend the substitution of the current IEEE draft." The comments accompanying the affirmative votes from Netherlands and the USA and the comments accompanying the negative votes from Germany and the United Kingdom are attached. __________ end of overall summary; beginning of detail summary ______ ISO/IEC JTC1/SC22 LETTER BALLOT SUMMARY PROJECT NO: JTC 1.22.21.04.01.01 SUBJECT: PDAM Approval for PDAM7 to IS 9945-1: Information technology - Portable Operating System Interface (POSIX) - Part 1: System Application Program Interface (API) - Amendment 7: Advanced Realtime Extensions (C Language) Reference Document No: N2678 Ballot Document No: N2678 Circulation Date: 04-07-1998 Closing Date: 07-24-1998 Circulated To: SC22 P Circulated By: Secretariat SUMMARY OF VOTING AND COMMENTS RECEIVED Approve Disapprove Abstain Comments Not Voting 'P' Members Australia (X) ( ) ( ) ( ) ( ) Austria ( ) ( ) ( ) ( ) (X) Belgium (X) ( ) ( ) ( ) ( ) Brazil ( ) ( ) ( ) ( ) (X) Canada (X) ( ) ( ) (X) ( ) China (X) ( ) ( ) ( ) ( ) Czech Republic ( ) ( ) ( ) ( ) (X) Denmark (X) ( ) ( ) ( ) ( ) Egypt (X) ( ) ( ) ( ) ( ) Finland (X) ( ) ( ) ( ) ( ) France ( ) ( ) (X) (X) ( ) Germany ( ) (X) ( ) (X) ( ) Ireland (X) ( ) ( ) ( ) ( ) Japan ( ) ( ) ( ) ( ) (X) Netherlands (X) ( ) ( ) (X) ( ) Norway (X) ( ) ( ) ( ) ( ) Romania ( ) ( ) ( ) ( ) (X) Russian Federation (X) ( ) ( ) ( ) ( ) Slovenia (X) ( ) ( ) ( ) ( ) UK ( ) (X) ( ) (X) ( ) Ukraine (X) ( ) ( ) ( ) ( ) USA (X) ( ) ( ) (X) ( ) 'O' Members Voting Korea Republic (X) ( ) ( ) ( ) ( ) Sweden ( ) ( ) (X) (X) ( ) __________ end of overall summary; beginning of Germany Comments ______ Germany disapproves with the following comment: We understand that BSI/U.K. is preparing a set of comments. Our vote will automatically change to approval when these comments will have been satisfactorily resolved. DDN, Berlin, 1998-07-10 ______ end of Germany Comments; beginning of Netherlands Comments _____ From: John Bijlsma (John.Bijlsma@nni.ni) Subject: NNI's votes for ISO/IEC JTC 1 SC22 N2678 APPROVAL WITH COMMENTS: Also the latest version of IS 9945-1, namely ISO/IEC 9945-1:1996, is proposed to be mentioned in par 1.2 on Normative References this Amendment still is composed as changes to the 1990-version of IS 9945-1 (compare page VI of this PDAM) The comment of the Netherlands is that the proposed changes in an Amendment should refer to the contents of the latest version of a base document. Furtheron the Netherlands wonder why in a ISO/IEC document a draft of an IEEE document should be referenced as is proposed on page 2 of this PDAM concerning document IEEE P1003.1d/D10. A latest comment deals with the use of the undeclared item "POSIX.1" on page 1 of this PDAM. ___________ end of Netherlands comments; beginning of UK comments _____ From Suzanne_Davison@BSI.ORG.UK Fri Jul 24 11:24:23 1998 Subject: UK Vote on SC22 N2678, PDAM Approval Ballot for PDAM7 to IS 9945-1 The UK votes NO for PDAM-7 to 9945-1 for the following reasons: @ 0 o 1 1 Sect 2.7.2 OBJECTION. page 6, line 100-107: Problem: (namespace pollution ) This is namespace pollution. See the position paper from the UK on this issue : WG15 N730: Reserved identifiers in POSIX standards. There are sufficient reserved prefixes for that can be used without the need to reserve any addtional prefixes. In particular we believe that mem_ and MEM_ will clash with existing applications. The new functionality in this proposed amendment should either use existing reserved prefixes (shm_ , MAP_ , MCL_ , MS_ or PROT_) or posix_ or POSIX_ as per the latest draft of 1003.1a. Action: This objection can be resolved by deleting this section on lines 97-107. @ 0 o 2 2 Sect 2.7.3 OBJECTION. page 7, line 130: Problem: ( namespace pollution ) The addition of the three functins typed_mem_open(), mem_offset() and typed_mem_get_info() is namespace pollution. Action: Either use an existing reserved prefix for function names or use the prefix posix_ as in posix_typed_mem_open(), posix_mem_offset(), posix_typed_mem_get_info() @ 0 o 3 3 Sect 2.9.3 Objection page 9, line 183-188: Problem: ( threads requirements) As well as requiring _POSIX_THREADS , support of these options should also require _POSIX_THREAD_SAFE_FUNCTIONS. The rationale is that a POSIX conforming system is expected also to support the Thread Safe Functions option, so lets mandate this. Action: Change the occurrences of "then the symbol {_POSIX_THREADS}" to "then the symbols {_POSIX_THREADS} and {_POSIX_THREAD_SAFE_FUNCTIONS}" @ 0 o 4 4 Sect 11.5.1.2 Objection page 26, line 86: Problem: ( threads header requirements) IEEE PASC Interpretation reference 1003.1c #46 identifies a problem with the existing POSIX.1-1996 specification with respect to the definition of the header. Many functions include only in their synopses, however it is clear that there are other headers required for a program to compile as per the synopses given. This problem occurs also in this specification and the same error should not be made twice. The header should be included before to define the types pthread_attr_t, pthread_cond_t, pthread_condattr_t, pthread_key_t, pthread_mutex_t, pthread_mutexattr_t, pthread_once_t, pthread_rwlock_t, pthread_rwlockattr_t, and pthread_t and the new types introduced in this amendment. This ties in with section 2.5 of POSIX 1003.1-1996. This problem also occurs in the following places: Section 11.5.2.1 line 163 Section 11.5.3.1 line 234 Section 11.6.1.1 line 343 Section 11.6.2.1 line 420 Section 11.6.3.1 line 487 Section 11.6.4.1 line 606 Section 11.6.5.1 line 708 Section 11.7.1.1 line 832 Section 11.7.2.1 line 899 Section 11.7.3.1 line 939 Action: Change the synopsis to be #include #include @ 0 o 5 5 Sect 11.6.3.2 Objection page 38, line 530: Problem: (Timeouts option) There is no "Timeouts" option. Action: Change "the Timeouts options" to "the Timers options" @ 0 o 6 6 Sect 11.6.4.2 Objection page 40, line 639: Problem: (Timeouts option 2) There is no "Timeouts" option. Action: Change "the Timeouts options" to "the Timers options" @ 0 o 6 6 Sect 12.2 Objection page 54-69, line 26-: Problem: (namespace pollution) The following new constants, structures and functions are all namespace pollution: The constants TYPED_MEM_ALLOCATE, TYPED_MEM_ALLOCATE_CONTIG, TYPED_MEM_MAP_ALLOCATABLE, The structure typed_mem_info, with the member tmi_length, The functions typed_mem_open(), mem_offset(), typed_mem_get_info() Action: Either use an existing reserved prefix for function names or use the prefix posix_ or POSIX_ @ 0 c 7 7 Sect B.12.4.1 Editorial comment page 62, line 324: Problem: (posix.1b conforming) There's no such things as a POSIX.1b conforming realtime system. POSIX.1b is not a standalone document as this phrase might suggest. There are POSIX.1 conforming systems and there are a set of options within a POSIX.1 conforming system. Action: This objection can be resolved either by Removing "POSIX.1b conforming" to leave "Realtime systems are expected..." Or to enumerate the POSIX.1 options required as in, "POSIX.1 conforming systems supporting the XXXX option, the YYYY option... etc" ____________________ end of UK comments; beginning of USA comments _____ From mdeane@ANSI.org Thu Jul 23 11:55:59 1998 Subject: US vote on SC 22 N 2678 Please accept the US vote on SC 22 N 2678, PDAM 7 to IS 9945-1: Information technology - Proposed Draft Amendment to ISO/IEC 9945-1 (POSIX)-Part 1: System Application Program Interface (API) - Amendment 7: Advanced Realtime Extensions (C Language). The US votes to APPROVE WITH COMMENTS. Comments on ballot for SC 22 N 2647: The section and line number references are against IEEE P1003.1j D6 Dated November 1997 It should be noted that the following comments also have been submitted to the IEEE Working Group developing IEEE P1003.1j. ---------------------------------------------------------------------- @ 0 o 1 1 Sect 2.7.2 OBJECTION. page 6, line 100-107: Problem: (namespace pollution ) This is namespace pollution. See the position paper from the UK on this issue : WG15 N730: Reserved identifiers in POSIX standards. There are sufficient reserved prefixes for that can be used without the need to reserve any addtional prefixes. In particular we believe that mem_ and MEM_ will clash with existing applications. The new functionality in this proposed amendment should either use existing reserved prefixes (shm_ , MAP_ , MCL_ , MS_ or PROT_) or posix_ or POSIX_ as per the latest draft of 1003.1a. Action: This objection can be resolved by deleting this section on lines 97-107. @ 0 o 2 2 Sect 2.7.3 OBJECTION. page 7, line 130: Problem: ( namespace pollution ) The addition of the three functins typed_mem_open(), mem_offset() and typed_mem_get_info() is namespace pollution. Action: Either use an existing reserved prefix for function names or use the prefix posix_ as in posix_typed_mem_open(), posix_mem_offset(), posix_typed_mem_get-info() @ 0 o 3 3 Sect 2.9.3 Objection page 9, line 183-188: Problem: ( threads requirements) As well as requiring _POSIX_THREADS , support of these options should also require _POSIX_THREAD_SAFE_FUNCTIONS. The rationale is that a POSIX conforming system is expected also to support the Thread Safe Functions option, so lets mandate this. Action: Change the occurrences of "then the symbol {_POSIX_THREADS}" to "then the symbols {_POSIX_THREADS} and {_POSIX_THREAD_SAFE_FUNCTIONS}" @ 0 o 4 4 Sect 11.5.1.2 Objection page 26, line 86: Problem: ( threads header requirements) IEEE PASC Interpretation reference 1003.1c #46 identifies a problem with the existing POSIX.1-1996 specification with respect to the definition of the header. Many functions include only in their synopses, however it is clear that there are other headers required for a program to compile as per the synopses given. This problem occurs also in this specification and the same error should not be made twice. The header should be included before to define the types pthread_attr_t, pthread_cond_t, pthread_condattr_t, pthread_key_t, pthread_mutex_t, pthread_mutexattr_t, pthread_once_t, pthread_rwlock_t, pthread_rwlockattr_t, and pthread_t and the new types introduced in this amendment. This ties in with section 2.5 of POSIX 1003.1-1996. This problem also occurs in the following places: Section 11.5.2.1 line 163 Section 11.5.3.1 line 234 Section 11.6.1.1 line 343 Section 11.6.2.1 line 420 Section 11.6.3.1 line 487 Section 11.6.4.1 line 606 Section 11.6.5.1 line 708 Section 11.7.1.1 line 832 Section 11.7.2.1 line 899 Section 11.7.3.1 line 939 Action: Change the synopsis to be #include #include @ 0 o 5 5 Sect 11.6.3.2 Objection page 38, line 530: Problem: (Timeouts option) There is no "Timeouts" option. Action: Change "the Timeouts options" to "the Timers options" @ 0 o 6 6 Sect 11.6.4.2 Objection page 40, line 639: Problem: (Timeouts option 2) There is no "Timeouts" option. Action: Change "the Timeouts options" to "the Timers options" @ 0 o 6 6 Sect 12.2 Objection page 54-69, line 26-: Problem: (namespace pollution) The following new constants, structures and functions are all namespace pollution: The constants TYPED_MEM_ALLOCATE, TYPED_MEM_ALLOCATE_CONTIG, TYPED_MEM_MAP_ALLOCATABLE, The structure typed_mem_info, with the member tmi_length, The functions typed_mem_open(), mem_offset(), typed_mem_get_info() Action: Either use an existing reserved prefix for function names or use the prefix posix_ or POSIX_ @ 0 c 7 7 Sect B.12.4.1 Editorial comment page 62, line 324: Problem: (posix.1b conforming) There's no such things as a POSIX.1b conforming realtime system. POSIX.1b is not a standalone document as this phrase might suggest. There are POSIX.1 conforming systems and there are a set of options within a POSIX.1 conforming system. Action: This objection can be resolved either by Removing "POSIX.1b conforming" to leave "Realtime systems are expected..." Or to enumerate the POSIX.1 options required as in, "POSIX.1 conforming systems supporting the XXXX option, the YYYY option... etc" ____________________ end of SC22 N2781 ______________________________