diff --git a/spec/getdns-0.382.tgz b/spec/getdns-0.382.tgz deleted file mode 100644 index 3d4a6afb..00000000 Binary files a/spec/getdns-0.382.tgz and /dev/null differ diff --git a/spec/getdns-0.383.tgz b/spec/getdns-0.383.tgz new file mode 100644 index 00000000..37162a1b Binary files /dev/null and b/spec/getdns-0.383.tgz differ diff --git a/spec/getdns_core_only.h b/spec/getdns_core_only.h index 9eda274d..32c18905 100644 --- a/spec/getdns_core_only.h +++ b/spec/getdns_core_only.h @@ -1,4 +1,4 @@ -/* Created at 2014-02-03-21-30-09*/ +/* Created at 2014-02-03-21-44-05*/ #ifndef GETDNS_H #define GETDNS_H diff --git a/spec/index.html b/spec/index.html index cec7fc75..ba30a3b1 100644 --- a/spec/index.html +++ b/spec/index.html @@ -293,8 +293,9 @@ href="#Contexts">later for more advanced use.
Supplies the reason for the callback. See below for the codes and reasons.
*response
A response object with the response data. This is described below. The response -object is part of the API's memory space, and will be freed by the API with the callback returns.
+A response object with the response data. +This is described below. +The application is responsible for cleaning up the response object with getdns_dict_destroy.
*userarg
Identical to the *userarg
passed to the calling function.
The helper getter functions return references to getdns_dict
, getdns_list
and getdns_bindata
data structures.
+The user must not destroy these retrieved "child" data structures themselves.
+They will automatically be destroyed when the containing "parent" data structure is destroyed.
+Also, retrieved "child" data structures can not be used any more after the containing "parent" data structure has been destroyed.
Some of the features of the API require that you create your own data structures to be used in
@@ -617,6 +623,9 @@ doesn't match the contents of the indexed argument or name. The list functions w
list. getdns_dict_remove_name()
will return
GETDNS_RETURN_NO_SUCH_DICT_NAME
if the name argument doesn't exist in the dict.
The helper setter functions store copies of the given "child" values. +It is the responsibility of the caller to dispose of the original values.
+Extensions are dict data structures. The names in the dict are the names of the extensions. @@ -2276,7 +2285,7 @@ The response dicts inherit the custom memory management functions and the value
There is a tarball that includes the .h files, +
There is a tarball that includes the .h files, the examples, and so on. The examples all make, even though there is no API implementation, based on a pseudo-implementation in the tarball; see make-examples-PLATFORM.sh. Note that this currently builds fine on the Macintosh and Ubuntu; help is definitely appreciated on making the build process