reading the (local) CA cert file to let users easier pinpoint the actual
problem. CURLE_SSL_CACERT_BADFILE (77) is the new libcurl error code.

the definitions for the return type and arguments types of functions
recv() and send().

stale by replacing loop counters with timeouts. In this way the
main loop of the test will be allowed to run up to 30 seconds on
any platform before aborting it.

(when the resoling isn't completede yet) and not confuse it with a simple
connection re-use (non-pipelined).

test hanging and actually is an indication that there's a condition that is
not being properly handled at some point in the library.

Loop counter limits might need to be further increased on false positives.

data is actually shown on screen. Like when you do 'curl -v host' with data
and debug info sent to the same terminal.

to verify winsock API availability.

using winsock or winsock2 API.

resolving is completed so we must make sure to survive it and mark the
connection as async (ie not yet connected completely).

ever actually are used

Get rid of non ANSI/ISO isascii().

could very well cause a negate number get passed in and thus cause reading
outside of the array usually used for this purpose.

We avoid this by using the uppercase macro versions introduced just now that
does some extra crazy typecasts to avoid byte codes > 127 to cause negative
int values.

#1579171

present, so there's no use to doing it again in this script!

even when using curl_multi_socket() or even using the multi_perform() when
relying on multi_timeout() to be good.

c-ares name resolves, but now we do!

cross-compiling) in order to detect problems with run-time libraries that
otherwise would occur when the sizeof tests for curl_off_t would run and
thus be much more confusing to users. The check of course should run after
all lib-checks are done and before any other test is used that would run an
executable built for testing-purposes.