Interpretations

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

IEEE Standards Interpretations for IEEE Std 1003.1b™-1993 IEEE Standard for Information Technology - Portable Operating System Interfaces (POSIX(R)) - Part 1: System Application Program Interface (API) - Amendment 1: Realtime Extension [C language]

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 #8
Topic: ftruncate Relevant Sections: 5.6.7.2 lines 1017-1018

This section states "The ftruncate() function marks the st_ctime and st_mtime fields of the file." Other interfaces such as write() have similar but different wording: ".. shall mark for update the st_ctime ... fields of the file." Are these phrases "marks the ... fields of the file" and "shall mark for update.." equivalent?

Interpretation Response
The meaning of the phases is the same. This is an editorial oversight and the committee has requested that the project editor change the first occurance to "...shall mark for update.." in section 5.6.7.2 line 1017.

Rationale for Interpretation
None.