full DATA has been sent, and I modified the test SMTP server to also send
  that response. As usual, the DONE operation that is made after a completed
  transfer is still not doable in a non-blocking way so this waiting for 250
  is unfortunately made blockingly.

fix compiler warning

fix compiler warning

fix compiler warning

fix compiler warning

fix compiler warning

- To allow an app to force a re-read of /etc/resolv.conf etc, pretty much
  like the res_init() resolver function offers

replaced tabs with spaces

fix Content-Length validation

fix compiler warning: conversion from "long" to "size_t" may lose sign

fix compiler warning: conversion from "long" to "size_t" may lose sign

  http://curl.haxx.se/mail/lib-2009-10/0024.html
  http://curl.haxx.se/bug/view.cgi?id=2944325

removed trailing whitespace

fix compiler warning

Overhauled test suite getpart() function. Fixing potential out of bounds
stack and memory overwrites triggered with huge test case definitions.

  (http://curl.haxx.se/bug/view.cgi?id=2951319)

moved gethostbyname_thread() to #else case to avoid 'not used' compiler warning.

  in the same RCPT TO line, when they should be sent in separate single
  commands. I updated test case 802 to verify this.

- I also fixed a bad use of my_setopt_str() of CURLOPT_MAIL_RCPT in the curl
  tool which made it try to output it as string for the --libcurl feature
  which could lead to crashes.

_ Upgrade OS400 EBCDIC wrappers for new options.
_ Upgrade ILE/RPG bindings to current state.

mention last changes

Steven M. Schweda updated VMS readme file

Steven M. Schweda removed batch_compile.com and defines.com

Steven M. Schweda fixed:

VMS builder bad behavior when used in a batch job.

Various ".LIS" and ".MAP" files created without being requested
by a "LIST" command-line option, and in the wrong place, too.

Some minor typographical changes.

- remove extra "\r\n" from doc404_RTSP

- avoid memory alignment issue when setting RTSP packet length

  to automatically uncompress it with the CURLOPT_ENCODING option, libcurl
  could wrongly provide the callback with more data than what the maximum
  documented amount. An application could thus get tricked into badness if the
  maximum limit was trusted to be enforced by libcurl itself (as it is
  documented).

  This is further detailed and explained in the libcurl security advisory
  20100209 at

    http://curl.haxx.se/docs/adv_20100209.html

warning fix

OOM handling fix