Answering questions that may arise related to the meaning of portions of an IEEE standard concerning specific applications.

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 #16
Topic: sigpending Relevant Clauses:, page 39 D10, lines 492-494

This section states that sigpending() returns the signals pending on "either" the process or the thread. The way stated, an implementation is allowed to return process pending signals or thread pending signals. An application cannot portably use and rely on what this function does because of "either". What the actual intent to say something more like "returns the union of the signals pending on the process and the calling thread"?

Interpretation Response
This is a duplicate. See Interpretation #3, part 12.

Rationale for Interpretation