From dcce39da3e6f7485dca39950dfc835563de3c3ea Mon Sep 17 00:00:00 2001 From: Kirill Volinsky Date: Mon, 25 Feb 2013 10:15:31 +0000 Subject: 1 step: libcurl static link git-svn-id: http://svn.miranda-ng.org/main/trunk@3763 1316c22d-e87f-b044-9b9b-93d7a3e3ba9c --- .../docs/libcurl/curl_global_cleanup.html | 61 ++++++++++++++++++++++ 1 file changed, 61 insertions(+) create mode 100644 plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_global_cleanup.html (limited to 'plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_global_cleanup.html') diff --git a/plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_global_cleanup.html b/plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_global_cleanup.html new file mode 100644 index 0000000000..afee7bcf39 --- /dev/null +++ b/plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_global_cleanup.html @@ -0,0 +1,61 @@ + + +curl_global_cleanup man page + + + + +

NAME

+

curl_global_cleanup - global libcurl cleanup

SYNOPSIS

+

#include <curl/curl.h> +

void curl_global_cleanup(void); +

DESCRIPTION

+

This function releases resources acquired by curl_global_init(3). +

You should call curl_global_cleanup(3) once for each call you make to curl_global_init(3), after you are done using libcurl. +

This function is not thread safe. You must not call it when any other thread in the program (i.e. a thread sharing the same memory) is running. This doesn't just mean no other thread that is using libcurl. Because curl_global_cleanup(3) calls functions of other libraries that are similarly thread unsafe, it could conflict with any other thread that uses these other libraries. +

See the description in libcurl(3) of global environment requirements for details of how to use this function. +

SEE ALSO

+

curl_global_init (3) libcurl (3) +

+ This HTML page was made with roffit. + -- cgit v1.2.3