🚀 go-pugleaf

Mark Jacobs wrote:
> Hi dude, my errorcode is a bit more informative :-

But not as informative as we would like to see it.
For instance you omit the code itself and the short
description.

>   ShowMessage(mjwinsockerr(ErrorCode)); ErrorCode=0;

First I thouht "He forgets to make ErrorCode zero". But then I saw
it at the end. Making ErrorCode zero suppresses the windowalert.
But only if you do it right away:

	ErrorCode=0; ShowMessage(mjwinsockerr(ErrorCode));

or more readable:

	ErrorCode=0;
	ShowMessage(mjwinsockerr(ErrorCode));

> And, now, I bet you're dying for the mjwinsockerr routine, which translates a
> Winsock error into an English description of what went wrong. Well, I'm in a
> kind mood today, so here it is :-

We all have such days ... Hope you get much more <g>. Have a nice day.

>     case 10060: return "!! A connection attempt failed because the connected
> party did not properly respond after a period of time, or established
> connection failed because connected host has failed to respond.";

10060 WSAETIMEDOUT

I'm missing 'timed out' in your description

	case 10060: return
		"10060 WSAETIMEDOUT The attempt to connect timed out.";

Hans.