Anonymous | Login | 2024-09-16 23:11 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Type | Date Submitted | Last Update | ||
0001127 | [1003.1(2013)/Issue7+TC1] Base Definitions and Headers | Editorial | Clarification Requested | 2017-03-15 21:36 | 2018-08-23 15:38 | ||
Reporter | jsm28 | View Status | public | ||||
Assigned To | |||||||
Priority | normal | Resolution | Rejected | ||||
Status | Closed | ||||||
Name | Joseph Myers | ||||||
Organization | |||||||
User Reference | |||||||
Section | sys/socket.h | ||||||
Page Number | 389 | ||||||
Line Number | 13239 | ||||||
Interp Status | --- | ||||||
Final Accepted Text | |||||||
Summary | 0001127: sys/socket.h inclusion of sys/uio.h | ||||||
Description |
The sys/socket.h specification says "The <sys/socket.h> header shall define the iovec structure as described in <sys/uio.h>." and "Inclusion of <sys/socket.h> may also make visible all symbols from <sys/uio.h>.". These statements (and the use of the iovec structure) are not XSI-shaded. However, the whole of sys/uio.h is XSI-shaded. Thus, when <sys/socket.h> is included in the non-XSI case (_POSIX_C_SOURCE=200809L), may declarations become visible of readv, writev and the symbols listed (also XSI-shaded) as reserved when <sys/uio.h> is included in XSH 2.2.2 The Name Space, or only of the iovec structure and its contents? |
||||||
Desired Action |
Clarify what may be visible when a non-XSI-shaded header is permitted to make visible symbols from an XSI-shaded header, or eliminate such permissions from the standard. |
||||||
Tags | No tags attached. | ||||||
Attached Files | |||||||
|
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |