Defect Report concerning: IEEE Std. 1003.1d-1999
Clause: 13.1
PASC Interpretation Ref: pasc-1003.1-108
Topic: timespec type in sched_param


This is an unapproved interpretation of PASC 1003.1d-1999.

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

Last update: 10 April,2001


							1003.1d-99  #108

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:			timespec type in sched_param
	Relevant Sections:	13.1



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


        Date: 2000 Jun 2

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

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

Advanced Realtime Extensions: IEEE Std 1003.1d-1999

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

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

1

Error=1 , Omission=2, Clarification=3

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

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

13.1, page 39

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

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


The description of the sched_ss_repl_period and
sched_ss_init_budget members of the sched_param structure
are defined as type "timespec".

This should be "struct timespec"

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

11  Solution proposed by the submitter (optional):

Change "timespec" to "struct timespec" for these two lines.




Interpretation response
------------------------
The standards states that the sched_ss_repl_period and
sched_ss_init_budget members of the sched_param structure should
be of type timespec and conforming implementations must conform to this. 
However, concerns have been raised about this which are being referred to 
the sponsor.

Rationale
-------------
The omission of "struct" prefix to timespec is an error.

Notes to project editor (not part of the interpretation):
------------------------
This should be fixed as in section 11.

Forwarded to Interpretations group: 2 June 2000
Proposed resolution: 2 June 2000
Finalised Interpretation: 25 July 2000