IEEE Standards Interpretations for IEEE Std 1003.2™-1992 IEEE Standard for Information Technology--Portable Operating System Interfaces (POSIX®)--Part 2: Shell and Utilities
Copyright © 1996 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 #97
Topic: set -o noclobber Relevant Clauses: 3.7.2
The standard says: [n] <word Output redirection using the > format shall fail if the noclobber option is set and the file named by the expansion of word exists and is a regular file. This does not specify what happens in the case of an empty regular file. What does the POSIX standard require? Should an error result in the case of empty as well as nonempty files?
The standard does not make a distinction between empty or non-empty files. Further, the standard clearly states that "Output redirection using the > format shall fail if the noclobgber option is set" and conforming implementations must conform to this.
Rationale for Interpretation