curl/docs/libcurl/curl_global_cleanup.3

.\" You can view this file with:
.\" nroff -man [file]
.\" $Id$
.\"
.TH curl_global_cleanup 3 "17 Feb 2006" "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(3)\fP.

You should call \fIcurl_global_cleanup(3)\fP once for each call you make to
\fIcurl_global_init(3)\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(3)\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(3)\fP of global environment requirements for
details of how to use this function.

.SH "SEE ALSO"
.BR curl_global_init "(3), "
.BR libcurl "(3), "
ripped out from ../ and put in its own directory now 2002-03-04 11:09:48 +01:00			`.\" You can view this file with:`
			`.\" nroff -man [file]`
			`.\" $Id$`
			`.\"`
fixed formatting 2006-02-17 14:31:49 +01:00			`.TH curl_global_cleanup 3 "17 Feb 2006" "libcurl 7.8" "libcurl Manual"`
ripped out from ../ and put in its own directory now 2002-03-04 11:09:48 +01:00			`.SH NAME`
formatting update to produce better links with the new roffit version 2004-02-27 16:34:06 +01:00			`curl_global_cleanup - global libcurl cleanup`
ripped out from ../ and put in its own directory now 2002-03-04 11:09:48 +01:00			`.SH SYNOPSIS`
			`.B #include <curl/curl.h>`
			`.sp`
			`.BI "void curl_global_cleanup(void);"`
			`.ad`
			`.SH DESCRIPTION`
fixed formatting 2006-02-17 14:31:49 +01:00			`This function releases resources acquired by \fBcurl_global_init(3)\fP.`
ripped out from ../ and put in its own directory now 2002-03-04 11:09:48 +01:00
fixed formatting 2006-02-17 14:31:49 +01:00			`You should call \fIcurl_global_cleanup(3)\fP once for each call you make to`
			`\fIcurl_global_init(3)\fP, after you are done using libcurl.`
Bryan Henderson turned the 'initialized' variable for curl_global_init() 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. 2006-01-16 00:55:53 +01:00
fixed formatting 2006-02-17 14:31:49 +01:00			`\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(3)\fP calls functions of other libraries that are`
			`similarly thread unsafe, it could conflict with any other thread that uses`
			`these other libraries.`
Bryan Henderson turned the 'initialized' variable for curl_global_init() 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. 2006-01-16 00:55:53 +01:00
fixed formatting 2006-02-17 14:31:49 +01:00			`See the description in \fBlibcurl(3)\fP of global environment requirements for`
			`details of how to use this function.`
ripped out from ../ and put in its own directory now 2002-03-04 11:09:48 +01:00
			`.SH "SEE ALSO"`
			`.BR curl_global_init "(3), "`
Bryan Henderson turned the 'initialized' variable for curl_global_init() 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. 2006-01-16 00:55:53 +01:00			`.BR libcurl "(3), "`
ripped out from ../ and put in its own directory now 2002-03-04 11:09:48 +01:00