Jeff King <peff@xxxxxxxx> writes: >> +DEVELOPER_CFLAGS += -Wno-error=deprecated-declarations > > That's a pretty broad hammer. And I think it may stomp on the hack to > rely on deprecated() in the UNUSED macro. > > As Ramsay suggested, we could probably use CURL_DISABLE_DEPRECATION to > limit this just to the problematic case. Yeah, I like that approach. But not this one ... > + CURL_IGNORE_DEPRECATION( > + curl_easy_setopt(result, CURLOPT_REDIR_PROTOCOLS, > + get_curl_allowed_protocols(0)); > + curl_easy_setopt(result, CURLOPT_PROTOCOLS, > + get_curl_allowed_protocols(-1)); > + ) > > though I think that was introduced only in 7.87.0 along with the > deprecation warnings themselves, so we'd need to have a fallback like: > > #ifndef CURL_IGNORE_DEPRECATION(x) > #define CURL_IGNORE_DEPRECATION(x) x > #endif ... as much.
