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. 3 Park Avenue New York, New York 10016-5997 USA All Rights Reserved.
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 #27
Topic: pthread_mutexattr_init Errors Relevant Clauses: 126.96.36.199, pthread_mutexattr_init Errors
pthread_attr_init and pthread_condattr_init both document ENOMEM as an "if occurs" error, but pthread_mutexattr_init documents ENOMEM as an "if detected" error. There is no reasonable justification for this difference, so clearly the specification of ENOMEM in the description of pthread_mutexattr_init was an oversight, and should be corrected.
The standard states that for the pthread_mutexattr_init() function ENOMEM is an "if detected" error and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor.
Rationale for Interpretation
This appears to be a defect.