diff options
| author | Viktor Szakats <commit@vsz.me> | 2022-06-13 18:59:45 +0000 |
|---|---|---|
| committer | Viktor Szakats <commit@vsz.me> | 2022-06-13 18:59:45 +0000 |
| commit | a94d6fe706721bdc63fe4e833e07249b88b1c208 (patch) | |
| tree | ebd7388c543c7a8495387c81f62da75dc1bd4731 /lib/version.c | |
| parent | 7ade9c50b35d95d47a43880c3097bebab7a7e690 (diff) | |
| download | curl-a94d6fe706721bdc63fe4e833e07249b88b1c208.tar.gz | |
version: rename threadsafe-init to threadsafe
Referring to Daniel's article [1], making the init function thread-safe
was the last bit to make libcurl thread-safe as a whole. So the name of
the feature may as well be the more concise 'threadsafe', also telling
the story that libcurl is now fully thread-safe, not just its init
function. Chances are high that libcurl wants to remain so in the
future, so there is little likelihood of ever needing any other distinct
`threadsafe-<name>` feature flags.
For consistency we also shorten `CURL_VERSION_THREADSAFE_INIT` to
`CURL_VERSION_THREADSAFE`, update its description and reference libcurl's
thread safety documentation.
[1]: https://daniel.haxx.se/blog/2022/06/08/making-libcurl-init-more-thread-safe/
Reviewed-by: Daniel Stenberg
Reviewed-by: Jay Satiro
Closes #8989
Diffstat (limited to 'lib/version.c')
| -rw-r--r-- | lib/version.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/version.c b/lib/version.c index ba957dcde..4672182d5 100644 --- a/lib/version.c +++ b/lib/version.c @@ -455,7 +455,7 @@ static curl_version_info_data version_info = { | CURL_VERSION_GSASL #endif #if defined(GLOBAL_INIT_IS_THREADSAFE) - | CURL_VERSION_THREADSAFE_INIT + | CURL_VERSION_THREADSAFE #endif , NULL, /* ssl_version */ |