[Ref: pasc-1003.1c-32] Topic: Thread-Specific Data Key Creation Description

Defect Report concerning: IEEE Std. 1003.1c-1995, ISO/IEC 9945-1:1990 AMD 2 - Threads
Clause: 17.1.1.2
PASC Interpretation Ref: pasc-1003.1c-32
Topic: Thread-Specific Data Key Creation Description

This is an unapproved interpretation of PASC 1003.1c-1995, ISO/IEC 9945-1:1990 AMD 2 - Threads.

Use of the information contained in this unapproved document is at your own risk.

Last update: 30 March,1998

								1003.1c-95  #32

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:               Thread-Specific Data Key Creation Description
	Relevant Sections:   17.1.1.2

Interpretation Request: (Defect Report)
-----------------------

	Date: Tue, 27 Aug 1996 15:27:10 -0400
	From: Dave Butenhof <butenhof@zko.dec.com>
        Standard: 9945-1:1996 (1003.1, 1996 Edition)


6. Section 17.1.1.2, 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.

        REF:    page 343, section 17.1.1.2, lines 20-33

Interpretation response
------------------------
This is a duplicate. See PASC P1003.1c Interpretation #8.

Rationale
-------------
None.
Forwarded to Interpretations group: August 29 1996
Proposed resolution: 18 Sep 96
Finalised: 25 Sep 96