Re: h_errno?

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 15 Feb 2013 21:44:54 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: dmantipov@yandex.ru, emacs-devel@gnu.org
> 
> > Date: Fri, 15 Feb 2013 11:09:14 -0800
> > From: Paul Eggert <eggert@cs.ucla.edu>
> > CC: Dmitry Antipov <dmantipov@yandex.ru>, emacs-devel@gnu.org
> > 
> > On 02/15/2013 02:19 AM, Eli Zaretskii wrote:
> > > I guess most of w32 functions that set h_errno can stop doing
> > > that now.
> > 
> > If memory serves, h_errno is part of an obsolete POSIX
> > interface that Emacs no longer uses now, if the platform
> > supports the current POSIX interface.  As I understand it,
> > the w32 code emulates the obsolete interface, so if the
> > policy is to emulate the interface rather than do the
> > minimal work needed to support Emacs, then w32 code needs to
> > set h_errno when it emulates that interface.
> 
> The problem is that (a) w32 code sets h_errno to values that come from
> errno.h, which is clearly wrong, and (b) it sets h_errno in many
> network functions that are not documented to set h_errno, like accept,
> recvfrom, sendto, listen, etc.  I will fix both of these soon.

Done in trunk revision 111804.