1999-02-15 Andreas Jaeger <aj@arthur.rhein-neckar.de>
* manual/llio.texi (Waiting for I/O): Correct meaning. Patch by
Jochen Voss <voss@mathematik.uni-kl.de> [PR libc/969].
* manual/setjmp.texi (Non-Local Exits and Signals): Fix
typo. Patch by Jochen Voss <voss@mathematik.uni-kl.de> [PR libc/970].
+1999-02-15 Andreas Jaeger <aj@arthur.rhein-neckar.de>
+
+ * manual/llio.texi (Waiting for I/O): Correct meaning. Patch by
+ Jochen Voss <voss@mathematik.uni-kl.de> [PR libc/969].
+
+ * manual/setjmp.texi (Non-Local Exits and Signals): Fix
+ typo. Patch by Jochen Voss <voss@mathematik.uni-kl.de> [PR libc/970].
+
1999-02-15 Ulrich Drepper <drepper@cygnus.com>
* string/Versions: Add __strverscmp to GLIBC_2.1.1.
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
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