Answering questions that may arise related to the meaning of portions of an IEEE standard concerning specific applications.

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 #18
Topic: stackaddr attribute Relevant Clauses:

Clause, page 141 D10, lines 79-83 A default value for the stackaddr attribute is not specified. The bahvior is specified if an application wants to specify their own stack. It does not specify what to do if they want the implementation to create a stack for them. Additionally, since a default value is not specified AND it is not specified that by default the implementation allocates a stack, the programmer must always check the default value of this attribute before creating a thread. What is the default value of this attribute? NULL to signify the user wants the implementation to allocate stacks?

Interpretation Response
This is a duplicate. See Interpretation #3, part 1.

Rationale for Interpretation