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 #4
Topic: pthread_atfork -- Headers and Functions Relevant Clauses: 126.96.36.199 lines 79-81, 2.7.3
Which header is the function pthread_atfork() defined in? Should it be pthread.h? At the moment this has been ommitted from that header. Was this intentional?
IEEE Std 1003.1b™-1993, to which IEEE Std 1003.1c-1995 is an amendment, on page 39 section 2.7.3 lines 1119 to 1121, states that "if a function is not listed below, it shall have its prototype appear in <unistd.h>...." pthread_atfork is not listed, so the standard is clear that it shall be listed in <unistd.h>.
Rationale for Interpretation