curl_share_strerror(3) [mojave man page]

curl_share_strerror(3)						  libcurl Manual					    curl_share_strerror(3)

NAME

       curl_share_strerror - return string describing error code

SYNOPSIS

       #include <curl/curl.h>
       const char *curl_share_strerror(CURLSHcode errornum);

DESCRIPTION

       The curl_share_strerror() function returns a string describing the CURLSHcode error code passed in the argument errornum.

AVAILABILITY

       This function was added in libcurl 7.12.0

RETURN VALUE

       A pointer to a zero terminated string.

SEE ALSO

       libcurl-errors(3), curl_multi_strerror(3), curl_easy_strerror(3)

libcurl 7.54.0							 February 03, 2016					    curl_share_strerror(3)

curl_global_cleanup(3)						  libcurl Manual					    curl_global_cleanup(3)

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 run-
       ning.  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.

CAUTION

       curl_global_cleanup(3)  does not block waiting for any libcurl-created threads to terminate (such as threads used for name resolving). If a
       module containing libcurl is dynamically unloaded while libcurl-created threads are still running then your program may crash or other cor-
       ruption	may occur. We recommend you do not run libcurl from any module that may be unloaded dynamically. This behavior may be addressed in
       the future.

SEE ALSO

       curl_global_init(3), libcurl(3), libcurl-thread(3),

libcurl 7.54.0							September 20, 2016					    curl_global_cleanup(3)