From 9dc81046dd9fffee4402dc32423a2984928271b7 Mon Sep 17 00:00:00 2001 From: Christopher Faylor Date: Fri, 30 Aug 2002 00:42:19 +0000 Subject: [PATCH] * how-api.texinfo: Remove a line from the CRLF discussion about lseek not working. Answer thread safe question more simply. --- winsup/doc/ChangeLog | 5 +++++ winsup/doc/how-api.texinfo | 8 ++------ 2 files changed, 7 insertions(+), 6 deletions(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 9ae1ba595..11ba8a92b 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,8 @@ +2002-08-29 Christopher Faylor + + * how-api.texinfo: Remove a line from the CRLF discussion about lseek + not working. Answer thread safe question more simply. + 2002-08-27 Nicholas Wourms * calls.texinfo: Add getc_unlocked, getchar_unlocked, putc_unlocked diff --git a/winsup/doc/how-api.texinfo b/winsup/doc/how-api.texinfo index b35ab4202..3ae60bbcb 100644 --- a/winsup/doc/how-api.texinfo +++ b/winsup/doc/how-api.texinfo @@ -75,18 +75,14 @@ Note that because the open/fopen switches are defined by ANSI, they exist under most flavors of Unix; open/fopen will just ignore the switch since they have no meaning to UNIX. -Also note that @code{lseek} only works in binary mode. - Explanation adapted from mailing list email by Earnie Boyd . @subsection Is the Cygwin library multi-thread-safe? -Multi-thread-safe support is turned on by default in 1.1.x releases -(i.e., in the latest net release). That does not mean that it is bug -free! +Yes. -There is also limited support for 'POSIX threads', see the file +There is also extensive support for 'POSIX threads', see the file @code{cygwin.din} for the list of POSIX thread functions provided. @subsection Why is some functionality only supported in Windows NT?