The change history is provided as an informative section, to track changes from earlier versions of this standard.
The following sections describe changes made to the System Interfaces volume of POSIX.1-2017 since Issue 6 of the base document. The CHANGE HISTORY section for each entry details the technical changes that have been made to that entry from Issue 5. Changes between earlier versions of the base document and Issue 5 are not included.
The following list summarizes the major changes that were made in the System Interfaces volume of POSIX.1-2017 from Issue 6 to Issue 7:
The Open Group Technical Standard, 2006, Extended API Set Part 1 is incorporated.
The Open Group Technical Standard, 2006, Extended API Set Part 2 is incorporated.
The Open Group Technical Standard, 2006, Extended API Set Part 3 is incorporated.
The Open Group Technical Standard, 2006, Extended API Set Part 4 is incorporated.
Existing functionality is aligned with ISO/IEC 9899:1999, Programming Languages - C, ISO/IEC 9899:1999/Cor.2:2004(E)
Austin Group defect reports, IEEE Interpretations against IEEE Std 1003.1, and responses to ISO/IEC defect reports against ISO/IEC 9945 are applied.
The Open Group corrigenda and resolutions are applied.
Features, marked legacy or obsolescent in the base document, have been considered for removal in this version.
The options within the standard have been revised.
The functions first introduced in Issue 7 (over the Issue 6 base document) are as follows:
The functions that were previously part of an option group but are now mandatory in Issue 7 are as follows:
The base functions moved to obsolescent status in Issue 7 (from the Issue 6 base document) are as follows:
|
Obsolescent Base Functions in Issue 7 |
|
|---|---|
The XSI functions moved to obsolescent status in Issue 7 (from the Issue 6 base document) are as follows:
|
Obsolescent XSI Functions in Issue 7 |
||
|---|---|---|
|
|
|
|
The functions and symbols removed in Issue 7 (from the Issue 6 base document) are as follows:
|
Removed Functions and Symbols in Issue 7 |
||
|---|---|---|
|
|
|
|
There is no additional rationale provided for this section.
Each system interface reference page has a common layout of sections describing the interface. This layout is similar to the manual page or "man" page format shipped with most UNIX systems, and each header has sections describing the SYNOPSIS, DESCRIPTION, RETURN VALUE, and ERRORS. These are the four sections that relate to conformance.
Additional sections are informative, and add considerable information for the application developer. EXAMPLES sections provide example usage. APPLICATION USAGE sections provide additional caveats, issues, and recommendations to the developer. RATIONALE sections give additional information on the decisions made in defining the interface.
FUTURE DIRECTIONS sections act as pointers to related work that may impact the interface in the future, and often cautions the developer to architect the code to account for a change in this area. Note that a future directions statement should not be taken as a commitment to adopt a feature or interface in the future.
The CHANGE HISTORY section describes when the interface was introduced, and how it has changed.
Option labels and margin markings in the page can be useful in guiding the application developer.
return to top of page