Ok, this is my take on extending Wez Furlong's idea/code/API.

I haven't yet decided if we really should proceed with returning a struct or
if we should instead go with a function that takes an option and returns info
for that particular option...

Any opinions?

/****************************************************************************
 * Structures for querying information about the curl library at runtime.
 */

/* declared as a struct to allow future expansion while remaining backwards
 * and binary compatible; any new fields in these two structs must be added
 * after the existing fields */
typedef struct {
  const char *protoname;
} curl_runtime_protocol_info;

typedef struct {
  const char *version; /* LIBCURL_VERSION */
  unsigned int version_num; /* LIBCURL_VERSION_NUM */
  int features; /* bitmask, see defines below */
  char *ssl_version; /* human readable string */
  long ssl_version_num; /* number */
  char *libz_version; /* human readable string */
  /* protocols is terminated by an entry with a NULL protoname */
  const curl_runtime_protocol_info *protocols;
} curl_version_info_data;

#define CURL_VERSION_IPV6 (1<<0)
#define CURL_VERSION_KERBEROS4 (1<<1)

/* returns a pointer to a static copy of the version info struct */
const curl_version_info_data *curl_version_info(void);

-- 
 Daniel Stenberg -- curl related mails on curl related mailing lists please
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf