From: Pádraig Brady Date: Fri, 28 Nov 2014 10:57:31 +0000 (+0000) Subject: doc: mention that _BSD_SOURCE is deprecated for _DEFAULT_SOURCE X-Git-Tag: v1.0~7249 X-Git-Url: https://gitweb.git.savannah.gnu.org/gitweb/?a=commitdiff_plain;h=8b62c05cf001f51aee062f541ece2aef6d580e03;p=gnulib.git doc: mention that _BSD_SOURCE is deprecated for _DEFAULT_SOURCE * doc/posix-functions/setjmp.texi: Defining _BSD_SOURCE will induce warnings unless _DEFAULT_SOURCE is also defined. --- diff --git a/doc/posix-functions/setjmp.texi b/doc/posix-functions/setjmp.texi index fbf6cc5b50..fbed1093cd 100644 --- a/doc/posix-functions/setjmp.texi +++ b/doc/posix-functions/setjmp.texi @@ -15,9 +15,9 @@ Portability problems not fixed by Gnulib: @item POSIX does not specify whether @code{setjmp} saves the signal mask in the @code{jmp_buf}. It does on BSD platforms, and on glibc platforms when -@code{_BSD_SOURCE} is defined; in this case @code{setjmp} behaves like -@code{sigsetjmp(.,1)}, and functions @code{_setjmp} and @code{_longjmp} are -available that don't save or restore the signal mask. On System V platforms -(excluding HP-UX), and on glibc platforms by default, @code{setjmp} doesn't -save the signal mask. +@code{_BSD_SOURCE} (and/or @code{_DEFAULT_SOURCE} on glibc >= 2.19) is defined; +in this case @code{setjmp} behaves like @code{sigsetjmp(.,1)}, and functions +@code{_setjmp} and @code{_longjmp} are available that don't save or restore +the signal mask. On System V platforms (excluding HP-UX), and on glibc +platforms by default, @code{setjmp} doesn't save the signal mask. @end itemize