docs: curl_version_info is not thread-safe before libcurl initialization

Closes #9583
This commit is contained in:
Patrick Monnerat 2022-09-25 17:30:23 +02:00 коммит произвёл Daniel Stenberg
Родитель e780aae77a
Коммит e1e482517f
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 5CC908FDB71E12C2
2 изменённых файлов: 6 добавлений и 0 удалений

Просмотреть файл

@ -46,6 +46,10 @@ Applications should use this information to judge if things are possible to do
or not, instead of using compile-time checks, as dynamic/DLL libraries can be
changed independent of applications.
This function can alter the returned static data as long as
\fIcurl_global_init\fP has not been called. It is therefore not thread-safe
before libcurl initialization occurs.
The curl_version_info_data struct looks like this
.nf

Просмотреть файл

@ -111,3 +111,5 @@ replacements, must be thread safe. You can use \fIcurl_global_init_mem(3)\fP
to set your own replacement memory functions.
.IP "Non-safe functions"
\fICURLOPT_DNS_USE_GLOBAL_CACHE(3)\fP is not thread-safe.
\fIcurl_version_info(3)\fP is not thread-safe before libcurl initialization.