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 © 1996 by the Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street New York, New York 10017 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 #24
Topic: schedpolicy etc Relevant Clauses: 188.8.131.52
1) Clause 184.108.40.206, page 122 D10, lines 333-342
A default value for the schedpolicy attribute is not specified.
What is the default value for this attribute?
2) Clause 220.127.116.11, page 122 D10, lines 353-357 A default value for the schedparam attribute is not specified. What is the default value for this attribute?
Implementations are already providing different values (drastically) which will effect portability. Some implementations consider the default value to be NULL; others return an actual value for this attribute as the default value. This case is not merely different default values, but actual differences in what this attribute represents. This impacts portability. What is the default value/behavior of this attribute?
This is a duplicate. See Interpretation #3, part 5.
Rationale for Interpretation