Re: Unknown Socket error (0+$!)

Report 0+$! when "$!" is "Unknown error" then look up the error number to find what the problem is (it will be a "winsock" error). (Long, sad story about trying to fix this long ago omitted.)

- tye

Comment on Re: Unknown Socket error (0+$!)

Replies are listed 'Best First'.
Re^2: Unknown Socket error (0+$!) by ikegami (Patriarch) on Jan 26, 2009 at 20:33 UTC
then look up the error number to find what the problem is Would using `$^E` work?	[reply] [d/l]
Re^3: Unknown Socket error (!$^E) by tye (Sage) on Jan 26, 2009 at 21:06 UTC
No, winsock errors are not covered by GetLastError() nor errno/strerror(). I've never even seen a "look up text based on error code" function for winsock errors (you can read winsock.h or STFW, of course). - tye	[reply]