CPU_SET.3, INFINITY.3, __ppc_get_timebase.3, __ppc_set_ppr_med.3, __ppc_yield.3,...

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

diff --git a/man3/atexit.3 b/man3/atexit.3
index 044d8a952e5243489c5bba19d9cd9df1b11141a1..6c1176f92e56e5197d1384cb6ab2a32ec82718fb 100644 (file)
--- a/man3/atexit.3
+++ b/man3/atexit.3
@@ -51,7 +51,7 @@ or via return from the program's
 .IR main ().
 Functions so registered are called in
 the reverse order of their registration; no arguments are passed.
-
+.PP
 The same function may be registered multiple times:
 it is called once for each registration.
 .LP
@@ -86,7 +86,7 @@ T{
 .BR atexit ()
 T}     Thread safety   MT-Safe
 .TE
-
+.sp 1
 .SH CONFORMING TO
 POSIX.1-2001, POSIX.1-2008, C89, C99, SVr4, 4.3BSD.
 .SH NOTES
@@ -96,14 +96,14 @@ Functions registered using
 .BR on_exit (3))
 are not called if a process terminates abnormally because
 of the delivery of a signal.
-
+.PP
 If one of the functions registered functions calls
 .BR _exit (2),
 then any remaining functions are not invoked,
 and the other process termination steps performed by
 .BR exit (3)
 are not performed.
-
+.PP
 POSIX.1 says that the result of calling
 .\" POSIX.1-2001, POSIX.1-2008
 .BR exit (3)
@@ -121,7 +121,7 @@ portable programs should not invoke
 .BR exit (3)
 inside a function registered using
 .BR atexit ().
-
+.PP
 The
 .BR atexit ()
 and
@@ -130,7 +130,7 @@ functions register functions on the same list:
 at normal process termination,
 the registered functions are invoked in reverse order
 of their registration by these two functions.
-
+.PP
 According to POSIX.1, the result is undefined if
 .BR longjmp (3)
 is used to terminate execution of one of the functions registered