On Mon, 29 Oct 2018, Rich Gray via curl-library wrote:
For example, if I coded something last year against libcurl 7.55.1,
somewhere early on there might be a call like:
curl_coded_for_version(0x075501);
This is an interesting idea, but I fear it is highly impractical and hard to
"When you come to a fork in the road, take it." - Yogi Berra [1]
Several times I've watch the project struggle with a desired libcurl
behavioral change due to concerns about backward compatibility. Currently,
there is a discussion about SSL host verification [2] which has this feel. I