On Fri, 14 Feb 2003, Martin C. Martin wrote:

> Yes. The only question is what to do if waitconnect() returns -1. That
> happens if select() returns -1. I assume in that case you don't want to
> keep calling select() over and over again, but rather signal an error.
> So, the if should really be:
>
> else if (2 == rc || -1 == rc)
>
> or simply
>
> else if (1 != rc)

Very true. I doubt that situation is very likely to ever occur though, but
I'll make it check for it anyway of course.

> While you're at it, you might want to change the comment above
> waitconnect(), to mention that it can return 2 if there's an error.

Yeps, I edited the comment to mention all possible return codes now.

Thanks!

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en