From rinehuls@Radix.Net Tue Nov 16 23:15:50 1999 Received: from mail1.radix.net (mail1.radix.net [207.192.128.31]) by dkuug.dk (8.9.2/8.9.2) with ESMTP id XAA35910; Tue, 16 Nov 1999 23:15:49 +0100 (CET) (envelope-from rinehuls@Radix.Net) Received: from saltmine.radix.net (saltmine.radix.net [207.192.128.40]) by mail1.radix.net (8.9.3/8.9.3) with SMTP id RAA18425; Tue, 16 Nov 1999 17:17:15 -0500 (EST) Date: Tue, 16 Nov 1999 17:17:12 -0500 (EST) From: William Rinehuls To: sc22info@dkuug.dk cc: keld simonsen Subject: SC22 N3037 - Disposition of Comments Report for PDAM7 to 9945-1 - POSIX API Advanced Realtime Extension (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 N3037 TITLE: Disposition of Comments Report for PDAM7 to ISO/IEC IS 9945-1: Information technology - Portable Operating System Interface (POSIX) - Part 1: System Application Program Interface (API) - Amendment 7: Advanced Realtime Extension (C Language) DATE ASSIGNED: 1999-11-16 SOURCE Secretariat, ISO/IEC JTC 1/SC22 BACKWARD POINTER: N/A DOCUMENT TYPE: Disposition of Comments Report PROJECT NUMBER: JTC 1.22.21.04.01.01 STATUS: N/A ACTION IDENTIFIER: FYI DUE DATE: N/A DISTRIBUTION: text CROSS REFERENCE: N2678, N2781 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@radix.net ______________ end of title page; beginning of report __________________ DISPOSITION OF COMMENTS REPORT 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) 20 comments were received on the PDAM ballot, with 1 from Germany, 3 from The Netherlands, 8 from the U.S., and 8 from Great Britain. The Netherlands Comment Response ================================ Comment 1 --------- 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. Response -------- Accept. Recommended action ------------------- Revise the next draft of the document according to requested change. Comment-2 --------- 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. Response -------- The reference to a draft standard is included because in the plan for POSIX standard approval it is expected that P1003.1d will be completed before PDAM7 to IS 9945-1. PDAM7 to IS 9945-1 amends some functions that appear in P1003.1d. Recommended action ------------------- Add a note to the next draft of the document specifying that the reference to P1003.1d is subject to its approval before the approval of this standard. If kept, it will reflect the final approved standard. Comment-3 --------- A latest comment deals with the use of the undeclared item "POSIX.1" on page 1 of this PDAM. Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. US Comment Response: ==================== Comment-1 --------- @ 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. Response -------- Accept Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-2 --------- @ 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() Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-3 --------- @ 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}" Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-4 --------- @ 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 Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-5 --------- @ 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" Response -------- The "Timeouts" option appears in P1003.1d, which appears as a normative reference for PDAM7 to IS 9945-1. PDAM7 to IS 9945-1 is amending ISO/IEC 9945-1:1996 as amended by P1003.1a and P1003.1d. The option needed in this part of the document is the "Timeouts" option, and *not* the "Timers" option. Recommended action ------------------- None. Comment-6 --------- @ 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" Response -------- The "Timeouts" option appears in P1003.1d, which appears as a normative reference for PDAM7 to IS 9945-1. PDAM7 to IS 9945-1 is amending ISO/IEC 9945-1:1996 as amended by P1003.1a and P1003.1d. The option needed in this part of the document is the "Timeouts" option, and *not* the "Timers" option. Recommended action ------------------- None. Comment-7 --------- @ 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_ Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-8 --------- @ 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" Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Great Britain Comment Response: =============================== Comment-1 --------- @ 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. Response -------- Accept Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-2 --------- @ 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() Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-3 --------- @ 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}" Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-4 --------- @ 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 Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-5 --------- @ 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" Response -------- The "Timeouts" option appears in P1003.1d, which appears as a normative reference for PDAM7 to IS 9945-1. PDAM7 to IS 9945-1 is amending ISO/IEC 9945-1:1996 as amended by P1003.1a and P1003.1d. The option needed in this part of the document is the "Timeouts" option, and *not* the "Timers" option. Recommended action ------------------- None. Comment-6 --------- @ 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" Response -------- The "Timeouts" option appears in P1003.1d, which appears as a normative reference for PDAM7 to IS 9945-1. PDAM7 to IS 9945-1 is amending ISO/IEC 9945-1:1996 as amended by P1003.1a and P1003.1d. The option needed in this part of the document is the "Timeouts" option, and *not* the "Timers" option. Recommended action ------------------- None. Comment-7 --------- @ 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_ Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-8 --------- @ 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" Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Germany Comment Response: ========================= Comment-1 --------- @ 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. Response -------- Accept Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-2 --------- @ 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() Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-3 --------- @ 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}" Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-4 --------- @ 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 Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-5 --------- @ 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" Response -------- The "Timeouts" option appears in P1003.1d, which appears as a normative reference for PDAM7 to IS 9945-1. PDAM7 to IS 9945-1 is amending ISO/IEC 9945-1:1996 as amended by P1003.1a and P1003.1d. The option needed in this part of the document is the "Timeouts" option, and *not* the "Timers" option. Recommended action ------------------- None. Comment-6 --------- @ 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" Response -------- The "Timeouts" option appears in P1003.1d, which appears as a normative reference for PDAM7 to IS 9945-1. PDAM7 to IS 9945-1 is amending ISO/IEC 9945-1:1996 as amended by P1003.1a and P1003.1d. The option needed in this part of the document is the "Timeouts" option, and *not* the "Timers" option. Recommended action ------------------- None. Comment-7 --------- @ 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_ Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. Comment-8 --------- @ 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" Response -------- Accept. Recommended action ------------------- This comment has already been addressed in PDAM7 to IS 9945-1/D7. _____________________ end of SC22 N3037 _____________________________