Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 11 Oct 2005 18:16:49 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: gethostbyname_r Message-ID: <20051011161649.GJ12938@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20051011143306.GI12938@calimero.vinschen.de> <434BE411.4060702@air2web.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <434BE411.4060702@air2web.com> User-Agent: Mutt/1.4.2i On Oct 11 12:10, Richard Campbell wrote: > Brian Ford wrote: > > > >There is almost no need for gethostbyname_r on Cygwin since its sole > >purpose is to create a thread safe interface. In most all cases, Cygwin's > >gethostbyname is thread safe. > > > > http://www.cygwin.com/ml/cygwin/2004-05/msg00202.html > > 1) Resolving a numeric host is more common than whatever (all - "most > all") is, IMO. > 2) The difference between most all and all is usually horrible to track > down. gethostbyname_r is a non-standard interface anyway. It only exists in glibc. The portable way to do this is to create a wrapper function in the application which handles access from multiple threads. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/