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 #34
Topic: SIGPOLL XSR option Relevant Sections: XBD signal.h
STREAMS support is optional and interfaces directly related to streams are shaded [XSR] throughout the standard. For example, stropts.h, isastream, getmsg, getpmsg, ioctl, putmsg, putpmsg, fattach, fdetach are all shaded [XSR]. SIGPOLL is defined in signal.h Aside from signal.h, SIGPOLL is only ever discussed in XSR related text. Since the SIGPOLL signal is only used by the above STREAMS interfaces, we think it should be shaded [XSR] in signal.h. Currently SIGPOLL is [XSI]. SIGPOLL references in signal.h should be shaded [XSR].
The standards states the requirements for SIGPOLL to be supported as part of the XSI option, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor.
Rationale for Interpretation
The semantics of SIGPOLL are only specified with functionality in the XSR option.