* Set "feature test macros" in italics when introducing it as a technical term. * Tighten cross reference. It wastes words to tell people to look elsewhere "for further information". Why else would they look there? * Use passive voice less. * Relocate sentence for more coherent discussion. * wfix: application _programming_ interface Signed-off-by: G. Branden Robinson <g.branden.robinson@xxxxxxxxx> --- man3/intro.3 | 27 +++++++++++++++------------ 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/man3/intro.3 b/man3/intro.3 index 3bf5035cf..d2c8c132e 100644 --- a/man3/intro.3 +++ b/man3/intro.3 @@ -36,13 +36,14 @@ the programmer must define a feature test macro in order to obtain the declaration of a function from the header file specified in the man page SYNOPSIS section. (Where required, -these feature test macros must be defined before including +these +.I feature test macros +must be defined before including .I any header files.) In such cases, -the required macro is described in the man page. -For further information on feature test macros, -see +the relevant function's man page describes the required macro. +See .BR \%feature_test_macros (7). .\" .\" There @@ -75,9 +76,16 @@ see .\" Various special libraries. The manual pages documenting their functions .\" specify the library names. .SS Subsections -Section 3 of this manual is organized into subsections +The Linux +.I man-pages +organize section 3 into subsections that reflect the complex structure of the standard C library -and its many implementations: +and its many implementations. +.IR libc 's +difficult history frequently makes it a poor example to follow +in design, +implementation, +and presentation. .IP \(bu 3 3const .IP \(bu @@ -85,11 +93,6 @@ and its many implementations: .IP \(bu 3type .PP -This difficult history frequently makes it a poor example to follow -in design, -implementation, -and presentation. -.PP Ideally, a library for the C language is designed such that each header file @@ -99,7 +102,7 @@ and exposes only data types and constants that are required for use of those functions. Together, these are termed an API or -.IR "application program interface" . +.IR "application programming interface" . Types and constants to be shared among multiple APIs should be placed in header files that declare no functions. This organization permits a C library module -- 2.30.2
Attachment:
signature.asc
Description: PGP signature
