curl_global_cleanup man page

From ac48668a549fe76648e0ac3f93c9943383e043f5 Mon Sep 17 00:00:00 2001 From: Kirill Volinsky Date: Sun, 10 Nov 2013 18:02:01 +0000 Subject: curl folder renamed git-svn-id: http://svn.miranda-ng.org/main/trunk@6858 1316c22d-e87f-b044-9b9b-93d7a3e3ba9c --- .../docs/libcurl/curl_global_cleanup.html | 61 ---------------------- 1 file changed, 61 deletions(-) delete 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 deleted file mode 100644 index afee7bcf39..0000000000 --- a/plugins/FTPFileYM/curl-7.29.0/docs/libcurl/curl_global_cleanup.html +++ /dev/null @@ -1,61 +0,0 @@ - - -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. -

NAME

SYNOPSIS

DESCRIPTION

SEE ALSO