assume that the curl file is a proper binary, it is often a script file
produced by libtool.

pointer!

overflow on 32bit filesize-systems

render a build impossible

are transfered. The maximum size we support now is 8 exabytes, which equals
to 8192 petabytes...

from 64 bit types to 32 bit ones

returns and uses as input and converting to signed generates warnings and
actually risks loss of accuracy

enabled builds

for the return code

ones use this too...

for a reason I don't know

out of memory (thanks to 'runtests.pl -t')

of using 'lud_filter' after freeing 'lud_dn'.

Patch for ldap.c under Windows. It works with wldap32.dll as supplied with
Win-98/ME/2000/XP, so no extra .dlls are required.  I've mostly tested it
against Verisign's ldap server. Added code in the case there are to many
responses (rc = LDAP_SIZELIMIT_EXCEEDED) and print only those we got. E.g.

curl
ldap://directory.verisign.net/?cn,display-name,mail,info?subtree?(cn=*Nelson*)

will print the first 10 results.

My only problem with it is that ldap_search_s() fails with "filter error" when
CURLDEBUG is defined ?! Maybe someone can spot the error.