From d07e37e2df789c2b1a707ff6fae3e7814bee60ab Mon Sep 17 00:00:00 2001 From: Ulrich Drepper Date: Mon, 15 Feb 1999 09:25:37 +0000 Subject: Update. 1999-02-15 Andreas Jaeger * manual/llio.texi (Waiting for I/O): Correct meaning. Patch by Jochen Voss [PR libc/969]. * manual/setjmp.texi (Non-Local Exits and Signals): Fix typo. Patch by Jochen Voss [PR libc/970]. --- manual/llio.texi | 2 +- manual/setjmp.texi | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'manual') diff --git a/manual/llio.texi b/manual/llio.texi index eb78153af5..b7dbdefeb7 100644 --- a/manual/llio.texi +++ b/manual/llio.texi @@ -1559,7 +1559,7 @@ descriptors are checked to see if they are ready for writing; and the conditions. You can pass a null pointer for any of these arguments if you are not interested in checking for that kind of condition. -A file descriptor is considered ready for reading if it is at end of +A file descriptor is considered ready for reading if it is not at end of file. A server socket is considered ready for reading if there is a pending connection which can be accepted with @code{accept}; @pxref{Accepting Connections}. A client socket is ready for writing when diff --git a/manual/setjmp.texi b/manual/setjmp.texi index 6e3408c8c1..f6799912eb 100644 --- a/manual/setjmp.texi +++ b/manual/setjmp.texi @@ -176,7 +176,7 @@ In BSD Unix systems, @code{setjmp} and @code{longjmp} also save and restore the set of blocked signals; see @ref{Blocking Signals}. However, the POSIX.1 standard requires @code{setjmp} and @code{longjmp} not to change the set of blocked signals, and provides an additional pair of -functions (@code{sigsetjmp} and @code{sigsetjmp}) to get the BSD +functions (@code{sigsetjmp} and @code{siglongjmp}) to get the BSD behavior. The behavior of @code{setjmp} and @code{longjmp} in the GNU library is -- cgit 1.4.1