IEEE Standards Interpretations for IEEE Std 1003.1™-2001 IEEE Standard for Information Technology - Portable Operating System Interface (POSIX®)
Copyright © 2006 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 #39
Topic: pathchk -p, Filename Portability Relevant Sections: XCU pathchk, XBD Global Concepts
By intent (as shown in XCU page 698 lines 27053-27054), pathchk -p should succed only on pathnames that can be moved to any conforming system. However, the formal description neglects one case: file name components that begin with "-". Under the current strict reading of the standard, for example, the command "pathchk -p ./-" must succeed even though "./-" is not a portable pathname (see XBD section 4.6 page 98 line 3071).
After XCU page 696 line 26993, add a new bullet: * Contains any component whose first character is a hyphen.
The standards states the requirements for portable filenames and the behavior for the pathchk utility, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor.
Rationale for Interpretation
It is believed that the intent of the former POSIX.1-1990 and POSIX.2-1992 standards was that the constraint on use of the hyphen character as the first character of a portable filename is a constraint on application behavior and not on implementations, since applications might not work as expected when such a filename is passed as a command line argument.