mirror of
https://github.com/moparisthebest/curl
synced 2024-08-13 17:03:50 -04:00
4c35a40858
into a counter, and thus you can now do multiple curl_global_init() and you are then supposed to do the same amount of calls to curl_global_cleanup(). Bryan also updated the docs accordingly.
33 lines
1.0 KiB
Groff
33 lines
1.0 KiB
Groff
.\" You can view this file with:
|
|
.\" nroff -man [file]
|
|
.\" $Id$
|
|
.\"
|
|
.TH curl_global_cleanup 3 "28 May 2001" "libcurl 7.8" "libcurl Manual"
|
|
.SH NAME
|
|
curl_global_cleanup - global libcurl cleanup
|
|
.SH SYNOPSIS
|
|
.B #include <curl/curl.h>
|
|
.sp
|
|
.BI "void curl_global_cleanup(void);"
|
|
.ad
|
|
.SH DESCRIPTION
|
|
This function releases resources acquired by \fBcurl_global_init\fP.
|
|
|
|
You should call \fIcurl_global_cleanup()\fP once for each call you make
|
|
to \fIcurl_global_init\fP, after you are done using libcurl.
|
|
|
|
\fBThis function is not thread safe.\fP 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 \fBcurl_global_cleanup()\fP 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 \fBlibcurl\fP(3) of global environment
|
|
requirements for details of how to use this function.
|
|
|
|
.SH "SEE ALSO"
|
|
.BR curl_global_init "(3), "
|
|
.BR libcurl "(3), "
|
|
|