Re: [lwip-users] errno is not set in sockets.c

[Mason]

Simon wrote:

> Personally, I think it's correct that we do not change 'errno' without 
> explicitly enabling it: we don't want to mess with C library code that 
> uses 'errno' by default.

I cannot stress how strongly I disagree on this point.

I will take the discussion to lwip-dev by filing a bug.

NB: I think lwip is a great project, but let's face it, the
documentation is severely lacking. I wasted /hours/ tracking
down libcurl's failure to connect in non-blocking mode, only
to stumble upon this piddly, undocumented macro.

<sigh>

-- 
Regards.