Interpretations

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

IEEE Standards Interpretation for IEEE Std 1003.1™-1990 IEEE Standard for Information Technology--Portable Operating System Interfaces (POSIX®)

Copyright © 2001 by the Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue New York, New York 10016-5997 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 #105
Topic:
posix_spawn_file_actions_addopen Relevant Sections: 3.1.4.2 PASC

1003.1d, Section 3.1.4.2 , the description of posix_spawn_file_actions_addopen does not say whether the function has to make a copy of the path parameter or whether it can store the pointer and assume the application does not destroy or alter the copy of the string.

We'd propose similar handling as for attributes to pthread_create() (but do not have specifics).

Interpretation Response
The standard does not speak to this issue, and as such no conformance distinction can be made between alternative implementations based on this. This is being referred to the sponsor.

Rationale for Interpretation
This is an unaddressed issue. It is recommended that this be addressed in the next revision. Forwarded to Interpretations group: 21 May 2000 Proposed resolution: 25 July 2000 Finalized interpretation: 29 August 2000