mirror of https://github.com/mkerrisk/man-pages
feature_test_macros.7: Emphasize that applications should not directly include <features.h>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
74b807b4d0
commit
6e558a81b8
|
@ -25,10 +25,6 @@
|
|||
.TH FEATURE_TEST_MACROS 7 2016-03-15 "Linux" "Linux Programmer's Manual"
|
||||
.SH NAME
|
||||
feature_test_macros \- feature test macros
|
||||
.SH SYNOPSIS
|
||||
.nf
|
||||
.B #include <features.h>
|
||||
.fi
|
||||
.SH DESCRIPTION
|
||||
Feature test macros allow the programmer to control the definitions that
|
||||
are exposed by system header files when a program is compiled.
|
||||
|
@ -45,10 +41,18 @@ Some feature test macros are useful for creating portable applications,
|
|||
by preventing nonstandard definitions from being exposed.
|
||||
Other macros can be used to expose nonstandard definitions that
|
||||
are not exposed by default.
|
||||
|
||||
The precise effects of each of the feature test macros described below
|
||||
can be ascertained by inspecting the
|
||||
.I <features.h>
|
||||
header file.
|
||||
.BR Note :
|
||||
applications do
|
||||
.I not
|
||||
need to directly include
|
||||
.IR <features.h> ;
|
||||
indeed, doing so is actively discouraged.
|
||||
See NOTES.
|
||||
.SS Specification of feature test macro requirements in manual pages
|
||||
When a function requires that a feature test macro is defined,
|
||||
the manual page SYNOPSIS typically includes a note of the following form
|
||||
|
|
Loading…
Reference in New Issue