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 #35
Topic: PATH_MAX Relevant Sections: 2.4 Classification: No Change required.
PATH_MAX appears to limit the length of a pathname as it is passed on a call to a function. There does not appear to be a defined Error Number in section 2.4 to address the situation when the pathname is less than or equal to PATH_MAX, but when combined with the current working directory exceeds the limit of the conforming implementation. It would appear such a definition should be added to ENAMETOOLONG.
No, the interpretations committee disagrees.
Rationale for Interpretation
The [ENAMETOOLONG] error condition refers to pathname arguments supplied to the implementation, not to any pathnames that might be internally generated by the implementation.