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 #40
Topic: streams & file descriptors & impl defined Relevant Sections: 8.2.3 Classification: No change

Interactions of Other File-Type C Functions (section 8.2.3) specifies 'single file description can be accessed both through streams and through file descriptors.' Section (pathname) 'A pathname that begins with two successive slashes may be interpreted in an implementation-defined manner.' Does this mean that the stream functions can behave in an implementation-defined manner? If all the S_IS* functions return false, are there any requirements on using the referenced file?

Interpretation Response
The implementation-defined semantics allowed by the text quoted from apply to the process of pathname resolution. Functions that use objects of type FILE * do their pathname resolution in an implementation-defined manner for pathnames that begin with two slashes followed by non-slash characters. does not apply to behavior other than that required for pathname resolution.

The behavior of file types that cannot be identified with the S_IS* macros ( is beyond the scope of IEEE Std 1003.1-1990.

Rationale for Interpretation