Hi - > But it isn't just about interference with other libcurl activity. If > you look at the curl_global_init code you see that it actually calls > a lot of code in other libraries. It is the curl_global_init code > that shouldn't be run in a multi-threaded environment. That it is > acceptable to others doesn't immediately make it safe to use in our > case. [...]
OK, I guess. Such concerns would be even better directed at the libraries that libcurl is using internally. > I assume you mean the second part. The attached is what I would propose > for the first part. Do you think that is a bad idea? It's mostly harmless, so if you like it, go for it. - FChE
