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 #13
Topic: sigevent structure Relevant Clauses: (IEEE Std 1003.1b-1993)

Clause --None in P1003.1c D10, corresponding section in IEEE Std 1003.1b-1993 is The behavior is specified when a sigevent structure of type SIGEV_NONE or type SIGEV_SIGNAL is passed. POSIX.1c does not specify what the behavior is if the sigevent structure specifies SIGEV_THREAD. The behavior needs to be specified. According to the current definitions, these functions are not required to support SIGEV_THREAD, even if POSIX_THREADS is defined. They define SIGEV_SIGNAL AND SIGEV_NONE, but not SIGEV_THREAD.

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

Rationale for Interpretation