setjmp.3: Repair changes to description of pre-2.19 glibc default behavior

The changes in commit 2ae4c26dec0497 were a mistake.
The System V behavior was always the default for setjmp(3).

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man3/setjmp.3 b/man3/setjmp.3
index 9cef3b9d87ac16d0ebf0560d14edacb54016d372..6b09c627bc9daaec3d016d21d85f1195756b1e05 100644 (file)
--- a/man3/setjmp.3
+++ b/man3/setjmp.3
@@ -172,9 +172,11 @@ that will not.
 The behavior under Linux depends on the glibc version
 and the setting of feature text macros.
 On Linux with glibc versions before 2.19,
-the BSD behavior is provided if (as per the feature test macro defaults) the
+.BR setjmp ()
+follows the System V behavior by default,
+but the BSD behavior is provided if the
 .BR _BSD_SOURCE
-feature test macro is (explicitly or implicitly) defined and none of
+feature test macro is defined and none of
 .BR _POSIX_SOURCE ,
 .BR _POSIX_C_SOURCE ,
 .BR _XOPEN_SOURCE ,
@@ -182,8 +184,7 @@ feature test macro is (explicitly or implicitly) defined and none of
 .BR _GNU_SOURCE ,
 or
 .B _SVID_SOURCE
-is explicitly defined;
-otherwise, the System V behavior is provided.
+is defined.
 Since glibc 2.19,
 .IR <setjmp.h>
 exposes only the System V version of