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 12:44:33 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: gethostbyname_r Message-ID: <20051011164433.GB15402@trixie.casa.cgf.cx> Reply-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.5.8i On Tue, Oct 11, 2005 at 12:10:57PM -0400, 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. AFAIK, cygwin's gethostbyname is thread safe in all cases. cgf -- 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/