[Ref: pasc-1003.1c-27] Topic: pthread_mutexattr

Defect Report concerning: IEEE Std. 1003.1c-1995, ISO/IEC 9945-1:1990 AMD 2 - Threads
Clause: 11.3.1.4
PASC Interpretation Ref: pasc-1003.1c-27
Topic: pthread_mutexattr_init Errors

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  #27

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:               pthread_mutexattr_init Errors
	Relevant Sections:   11.3.1.4

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)


1. Section 11.3.1.4, 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.

        REF:    page 254, section 11.3.1.4, line 472
                page 260, section 11.4.1.4, line 685
                page 335, section 16.2.1.4, line 95


Interpretation response
------------------------

The standards 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
-------------

This appears to be a defect.

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