From ajosey@rdg.opengroup.org Mon Mar 30 12:46:30 1998 Received: from mailgate.rdg.opengroup.org (mailgate.rdg.opengroup.org [192.153.166.4]) by dkuug.dk (8.6.12/8.6.12) with SMTP id MAA05270 for ; Mon, 30 Mar 1998 12:46:27 +0200 Received: by mailgate.rdg.opengroup.org; id AA25825; Mon, 30 Mar 1998 10:45:42 GMT Message-Id: <9803301045.AA25825@mailgate.rdg.opengroup.org> Received: from mailhome [192.153.166.5] by mailgate.rdg.opengroup.org via smtpd ; Mon Mar 30 10:45 GMT 1998 Received: by mailhome.rdg.opengroup.org (1.36.108.10/16.2) id AA15149; Mon, 30 Mar 1998 11:45:06 +0100 From: ajosey@rdg.opengroup.org (Andrew Josey) Date: Mon, 30 Mar 1998 11:45:06 +0100 Reply-To: ajosey@rdg.opengroup.org (Andrew Josey) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: sc22wg15@dkuug.dk Subject: Defect Report concerning: IEEE Std. 1003.1-1996, ISO/IEC 9945-1:1996 - C API For the attention of the WG15 Project Editors: Defect Report concerning: IEEE Std. 1003.1-1996, ISO/IEC 9945-1:1996 - C API Defect report number: IS9945-1:1996#85 Clause: Subclause 3.3.1, P70 & subclause 3.3.8.1, P80 (sigtimedwait()) PASC Interpretation Ref: pasc-1003.1-85 Topic: signal.h and namespace ---------------------------------------------------------------------------- 1003.1-96 #85 _____________________________________________________________________________ Interpretation Number: XXXX Topic: signal.h and namespace Relevant Sections: Subclause 3.3.1, P70 & subclause 3.3.8.1, P80 (sigtimedwait()) Interpretation Request: (Defect Report) ----------------------- Date: Wed, 25 Feb 1998 11:22:12 -0600 From: Don.Cragun@eng.sun.com WG15 Status Block: ------------------------------------------------------------------------ 1 Defect report number: IS9945-1:1996#85 2 Submitter: IEEE PASC March 30 1998 3 Addressed to: JTC1/SC22 /WG15 editor's group on IS 9945-1 4 WG secretariat: ------------------------------------------------------------------------ 5 Date circulated by WG secretariat: 6 Deadline on response from editor: ------------------------------------------------------------------------ 7 Defect Report concerning (number and title of International Standard or DIS final text, if applicable): IEEE Std 1003.1-1996 (incorporates 1003.1-1990, 1003.1b-1993, 1003.1c-1995, 1003.1i-1995) (ISO 9945-1:1996) ------------------------------------------------------------------------ 8 Qualifier (e.g. error, omission, clarification required): 2 Error=1 , Omission=2, Clarification=3 ------------------------------------------------------------------------ 9 References in document (e.g. page, clause, figure, and/or table numbers): Subclause 3.3.1, P70 & subclause 3.3.8.1, P80 (sigtimedwait()) ------------------------------------------------------------------------ 10 Nature of defect (complete, concise explanation of the perceived problem): POSIX defines the sigtimedwait() function, which takes a const struct timespec * as one of it's arguments. This function is declared in the header. However, the synopsis for sigtimedwait() does not specify inclusion of which is where the timespec structure is defined. Likewise, the sigtimedwait() description does not state any requirements for defining struct timespec, nor does it allow for the visibility of symbols in when including . To include and not define struct timespec will result in compilers generating a warning about a dubious tag declaration for struct timespec. Though POSIX references in the Cross- References and See Also sections respectively, and talks about the timespec structure in the text, there is no indication as to how one should go about making this visible. ------------------------------------------------------------------------ 11 Solution proposed by the submitter (optional): Add a paragraph after POSIX.1-1996, P70, L50 (description of ): Inclusion of the header may make visible symbols allowed by this part of ISO/IEC 9945 to be in the header. (This matches the wording used on POSIX.1-1996, P319 for .) ------------------------------------------------------------------------ Interpretation response ------------------------ The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor. Rationale ------------- There appear to be some omissions in the specification. It is recommend that a future revision address this issue. ------------------------------------------------------------------------ 12 Editor's response (any material proposed for processing as a technical corrigendum to, an amendment to, or a commentary on the International Standard or DIS final text is attached separately to this completed report): See interpretation response attached Forwarded to Interpretations group: 26 Feb 1998 Finalised: 30 March 1998 ----- Andrew Josey PASC Functional Chair Interpretations The Open Group Apex Plaza,Forbury Road, Reading,Berks.RG1 1AX,England Tel: +44 118 9508311 ext 2250 Fax: +44 118 9500110 Email: a.josey@opengroup.org