code fine on ares!

to memdebug the ares stuff as well.

same channel during the whole curl handle's life until curl_easy_cleanup().

is a valid pointer, but instead always depend on the passed-in dns pointer.
This happens to be NULL when the connection is re-used...

and memset

to properly work with SOCKS5 proxies. I also included some ascii art describing
the SOCKS5 response, as RFC1928 describes. Jeff provided details in bug
report #741841 and here: http://curl.haxx.se/mail/lib-2004-02/0181.html

seems to correct some host cache screw-ups I could reproduce.

SO_BINDTODEVICE is present, to prevent compiler warnings about the variable

Removed some dates/names in the comments.

Curl_write in CURLcode, to keep the picky compilers happy

more" when the previous approach. Known to work on Linux, possibly on other
platforms as well.

sure this doesn't get weird on 64bit archs.

archs, also no longer typecast pointers to ints as that is a nono on 64bit
systems.

with anyway and thus caused picky compiler to warn.

getaddrinfo() implementation.

following a location. After discussions with Tim Baker.

we avoid it where possible.

The standards don't actually allow typecasts between data and functions so
some picky compilers warn about this.

chunky coding of uploads

picky compiler warnings

PORT
Provide better error messages to allow debugging if one if the ipv6-related
name functions fail in the ftp_use_port() function. This might help us
diagnose the problems on AIX. Also make sure getaddrinfo() uses NULL and
not "0" for the service argument.