[MLton] Socket.connectNB on NetBSD
Henry Cejtin
henry@sourcelight.com
Tue, 18 Nov 2003 23:54:11 -0600
The reason the connect should fail is only because the IP you told it to
connect to is 0, right? I.e., if the call to Socket.connectNB had had a
second parameter of 127.0.0.1 then it should have succeeded (eventually).
You might try, under NetBSD, to do a getsockname() and getpeername() after
the connect to see what it thinks it is connected to. Also, what happens
if you try exactly this in blocking mode?