Re: [Chicken-hackers] [PATCH] Fix nonblocking socket behaviour on Windows

[Peter Bex]

On Tue, Nov 26, 2013 at 01:24:55AM +0000, Mario Domenech Goulart wrote:
> Unfortunately it seems to break something on XP.  chicken-install gets a
> TCP timeout error instantly
> 
> Without this patch, I don't get the TCP timeout error.

Thanks to some pointers by "rivo" on IRC, and digging through the
MSDN docs, I've finally made a patch that fixes this stuff properly.
I also noticed whole swaths of code in posixwin.scm which weren't
used at all (so I deleted that), and decided to remove all support
for Winsock 1.  Winsock2 dates back to Windows 95, which we don't
support anymore.  Anything more recent than that is shipped with
Winsock 2 built-in.

Of course the patch is so complicated by now that it most definitely
should *NOT* go into stability.  But the process* fix should go in,
like I said in the other thread.

Question: should we rip out support for pre-NT versions of Windows
altogether?  I'm in favor, that would allow us to simplify
##sys#shell-command a bit, too (because get_shlcmd is pretty
complicated and checks with sysinfo() whether it's running on NT).

Cheers,
Peter
-- 
http://www.more-magic.net

0001-Several-Windows-related-fixes-and-one-race-condition.patch
Description: Text document

0002-Get-rid-of-all-fallback-winsock.h-code-and-simplify-.patch
Description: Text document