fanotify_init.2, fanotify.7: Document FAN_REPORT_TID

[thirdparty/man-pages.git] / man3 / assert_perror.3

diff --git a/man3/assert_perror.3 b/man3/assert_perror.3
index 94ca31f28f0747833f42cec80d96d8b3e6210cd7..b2340d00d610d94e33386ca37c76a723fea5d86e 100644 (file)
--- a/man3/assert_perror.3
+++ b/man3/assert_perror.3
@@ -1,5 +1,6 @@
 .\" Copyright (C) 2002 Andries Brouwer <aeb@cwi.nl>
 .\"
+.\" %%%LICENSE_START(VERBATIM)
 .\" Permission is granted to make and distribute verbatim copies of this
 .\" manual provided the copyright notice and this permission notice are
 .\" preserved on all copies.
@@ -19,18 +20,19 @@
 .\"
 .\" Formatted or processed versions of this manual, if unaccompanied by
 .\" the source, must acknowledge the copyright and authors of this work.
+.\" %%%LICENSE_END
 .\"
 .\" This replaces an earlier man page written by Walter Harms
 .\" <walter.harms@informatik.uni-oldenburg.de>.
 .\"
-.TH ASSERT_PERROR 3  2002-08-25 "GNU" "Linux Programmer's Manual"
+.TH ASSERT_PERROR 3  2017-09-15 "GNU" "Linux Programmer's Manual"
 .SH NAME
 assert_perror \- test errnum and abort
 .SH SYNOPSIS
 .nf
-.B #define _GNU_SOURCE
+.BR "#define _GNU_SOURCE" "         /* See feature_test_macros(7) */"
 .B #include <assert.h>
-.sp
+.PP
 .BI "void assert_perror(int " errnum );
 .fi
 .SH DESCRIPTION
@@ -52,13 +54,26 @@ is nonzero.
 The message contains the filename, function name and
 line number of the macro call, and the output of
 .IR strerror(errnum) .
-.SH "RETURN VALUE"
+.SH RETURN VALUE
 No value is returned.
-.SH "CONFORMING TO"
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lb lb lb
+l l l.
+Interface      Attribute       Value
+T{
+.BR assert_perror ()
+T}     Thread safety   MT-Safe
+.TE
+.sp 1
+.SH CONFORMING TO
 This is a GNU extension.
 .SH BUGS
-The purpose of the assert macros is to help the programmer find bugs in
-his program, things that cannot happen unless there was a coding mistake.
+The purpose of the assert macros is to help programmers find bugs in
+their programs, things that cannot happen unless there was a coding mistake.
 However, with system or library calls the situation is rather different,
 and error returns can happen, and will happen, and should be tested for.
 Not by an assert, where the test goes away when
@@ -66,9 +81,8 @@ Not by an assert, where the test goes away when
 is defined,
 but by proper error handling code.
 Never use this macro.
-.SH "SEE ALSO"
+.SH SEE ALSO
 .BR abort (3),
 .BR assert (3),
 .BR exit (3),
-.BR strerror (3),
-.BR feature_test_macros (7)
+.BR strerror (3)