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 © 1996by 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 #32
Topic: Thread-Specific Data Key Creation Description Relevant Clauses:

Clause, Thread-Specific Data Key Creation Description The description of thread-specific data destructors, somewhere along the line, lost the original intent of the working group, that the implementation shall set the thread-specific data value to NULL prior to calling the application's destructor routine. The standard currently (and incorrectly) requires that the application set the value to NULL within the destructor in order to avoid infinite looping or memory leakage. The standard should be corrected to require that the implementation SHALL set the value to NULL before calling the application destructor function.

Interpretation Response
This is a duplicate. See Interpretation #8.

Rationale for Interpretation