Windows doesn't recognize a connect to 0.0.0.0 request while linux (at
least) does.  The question is, do we want to support/emulate this or
declare it as non-portable/unsupported?

This is causing the mess in testsock.c test_get_addr deferred socket
connection test.

It also appears that sockets.c in MANY cases just fails to initialize
(local|remote)_interface_unknown, unless I'm imagining things.

Bill

Reply via email to