On Thu, 26 May 2022, Timothe Litt wrote:
Not clear why we need the CURL *handle to get just the (built-in) default
strings. The handle is ignored for these INFO codes, right?
curl_easy_getinfo() already exists and it works like this. I don't want to
introduce a whole new function just for these and even if the easy handle
doesn't mean anything for this use case, I don't want to complicated matters
by documenting this exception.
OTOH, if something was set for a handle by the user, it would be nice to get
that - e.g. for the "generate C code" or "generate curl command" APIs.
That's what I meant by "current bundle path for a handle". You could do both
with one INFO code per string.
We don't offer get methods for any other setopt, and I don't think we should
start doing it now. Applications can easily just "remember" what they set
options to on their own if they need that ability.
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://curl.se/support.html
--
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
