[API 0.385] User must free helper function allocs

This commit is contained in:
Willem Toorop 2014-02-03 22:01:27 +01:00
parent d8543591bc
commit f86f2a43da
4 changed files with 8 additions and 2 deletions

Binary file not shown.

BIN
spec/getdns-0.385.tgz Normal file

Binary file not shown.

View File

@ -1,4 +1,4 @@
/* Created at 2014-02-03-21-52-29*/ /* Created at 2014-02-03-22-00-41*/
#ifndef GETDNS_H #ifndef GETDNS_H
#define GETDNS_H #define GETDNS_H

View File

@ -1136,6 +1136,9 @@ getdns_convert_fqdn_to_dns_name(
); );
</div> </div>
<p>The returned values are allocated with the default system allocator (<code>malloc</code>).
The caller is responsible of disposing these allocations with free. </p>
<h1>5. Additional Definitions and Descriptions</h1> <h1>5. Additional Definitions and Descriptions</h1>
<h2>5.1 A Few Needed Definitions</h2> <h2>5.1 A Few Needed Definitions</h2>
@ -2060,6 +2063,9 @@ getdns_display_ip_address(
of the IPv4 or IPv6 address in it. The API determines they type of address of the IPv4 or IPv6 address in it. The API determines they type of address
by the length given in the bindata.</p> by the length given in the bindata.</p>
<p class=cont>All memory locations returned by these helper functions are allocated by the default system allocator (<code>malloc</code>).
The caller is responsible of disposing these allocations with <code>free</code>.</p>
<h1>8. <a id="Contexts">DNS Contexts</a></h1> <h1>8. <a id="Contexts">DNS Contexts</a></h1>
<p>Many calls in the DNS API require a DNS context. A DNS <p>Many calls in the DNS API require a DNS context. A DNS
@ -2421,7 +2427,7 @@ The response dicts inherit the custom memory management functions and the value
<h1>9. The Generated Files</h1> <h1>9. The Generated Files</h1>
<p>There is <a href="getdns-0.384.tgz">a tarball</a> that includes the .h files, <p>There is <a href="getdns-0.385.tgz">a tarball</a> that includes the .h files,
the examples, and so on. The examples all make, even though there is no API implementation, based 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 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 on the Macintosh and Ubuntu; help is definitely appreciated on making the build process