IEEE Standards Interpretations for IEEE Std 1003.1c™-1995 IEEE Standard for Information Technology--Portable Operating System Interface (POSIX(R)) - System Application Program Interface (API) Amendment 2: Threads Extension (C Language)
Copyright © 1996 by the Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street New York, New York 10017 USA All Rights Reserved.
These are interpretations of IEEE Std 1003.1c-1995.
Interpretations are issued to explain and clarify the intent of a standard and do not constitute an alteration to the original standard. In addition, interpretations are not intended to supply consulting information. Permission is hereby granted to download and print one copy of this document. Individuals seeking permission to reproduce and/or distribute this document in its entirety or portions of this document must contact the IEEE Standards Department for the appropriate license. Use of the information contained in this document is at your own risk.
IEEE Standards Department, Copyrights and Permissions, 445 Hoes Lane, Piscataway, New Jersey 08855-1331, USA
Interpretation Request #11
Topic: sigpending() Relevant Clauses: 188.8.131.52
Clause 184.108.40.206 states "are pending either for the process or the calling thread". The present wording text allows for implementations that differ severely and impacts application portability. This should be better restated as "the union of signals pending for the process and calling thread". The intent is to return the set of signals which are pending and may be processed by the calling thread, whether pending on the thread or the process (i.e., the union of the process and thread pending signals). By saying "either the process or the calling thread", an implementation is allowed to return one or the other. If system A returns pending signals for the calling thread, and system B returns pending signals for the process, applications will not be portable.
This needs clarification. We believe the wording could be better phrased as "the union of signals pending for the process and calling thread which are blocked from delivery for the calling thread"
This is a duplicate of Interpretation #3, part 12.
Rationale for Interpretation