Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <02b501c222a2$c8b9c7a0$6132bc3e@BABEL> From: "Conrad Scott" To: References: <3D23052F DOT 3020407 AT perathoner DOT de> Subject: Re: putc_unlocked in stdio.h but not in libs (1.3.11-3) Date: Wed, 3 Jul 2002 16:03:24 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 "Marcello Perathoner" wrote: > According to the FAQ putc_unlocked is not implemented > and you don't find it in the libraries. > But it is present in the stdio.h header. The level of synchronicity on this issue is starting to get me suspicious. Taking up Corinna's point from yesterday, none of the unexported functions from are SUSv3 functions, they're all BSD-isms. Then again, they are all just wrappers that call other (already exported) functions, so size isn't much of an issue and you don't get any extra funcionality. A more important point I've tripped over is that cygwin doesn't seem to provide implementations of the flockfile etc. functions used by stdio to lock the FILE objects, and so the current version is not thread-safe. Is that true? says I in some pain, having just gone through cygserver replacing all calls with calls to avoid a thread-safety problem in the C++ library :-( Just for the record, the list of unexported functions from is currently: getc_unlocked getchar_unlocked putc_unlocked putchar_unlocked setbuffer setlinebuf // Conrad -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/