Defect Report concerning: IEEE Std. 1003.1-1996, ISO/IEC 9945-1:1996 - C API
Clause: p78 line 870, p79 line 883
PASC Interpretation Ref: pasc-1003.1-111
Topic: signal concepts


This is an unapproved interpretation of PASC 1003.1-1996, ISO/IEC 9945-1:1996 - C API.

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

Last update: 10 April,2001


								1003.1-96  #111

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:			signal concepts
	Relevant Sections:	p78 line 870, p79 line 883



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

        Date: 2000 June 16
	Ref: XSH 20

------------------------------------------------------------------------ 

 7  Defect Report concerning (number and title of International Standard
    or DIS final text, if applicable): 

IEEE Std 1003.1-1996 (incorporates 1003.1-1990, 1003.1b-1993, 1003.1c-1995,
1003.1i-1995) (ISO 9945-1:1996)

------------------------------------------------------------------------ 

 8  Qualifier (e.g. error, omission, clarification required):

3

Error=1 , Omission=2, Clarification=3

------------------------------------------------------------------------ 

 9  References in document (e.g. page, clause, figure, and/or table
    numbers):

P78 L870
P79 L883

------------------------------------------------------------------------ 

10  Nature of defect (complete, concise explanation of the perceived
    problem):


At 870, there's the "with a single exception clause".
At 883 in the sentence beginning with "If" would seem to disallow
that exception.  (That is, if a return is executed by the handler,
all would seem to be required to work right, regardless of what
went before.)



------------------------------------------------------------------------ 

11  Solution proposed by the submitter (optional):

Replace the sentence with a pointer to the discussion of signal-safe
and unsafe functions.

------------------------------------------------------------------------ 



Interpretation response
------------------------
The standard is unclear on this issue, and no conformance distinction
can be made between alternative implementations based on this. This is
being referred to the sponsor.

Rationale
-------------
None.

Notes to project editor (not part of this interpretation):
------------------------------------------------------------
Add "except as ..." on line 870: "...except as noted
for unsafe functions".

Forwarded to Interpretations group: 19 June 2000
Proposed resolution: 25 July 2000
Finalised interpretation: 29 August 2000