Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
drop deprecation markers?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 22 Apr 2025 23:55:39 +0200 (CEST)
Hello team,
Someone on IRC pointed out that the typecheck-gcc checks don't work anymore. I
could reproduce and I started to fix them. I have a PR pending.
These typechecks warning outputs get pretty damaged by the deprecation
warnings, because they include checks for deprecated options.
This made me realize that I don't think our deprecation warnings do a lot of
good and that they mostly just annoy me when I run into them. We added them in
November 2022 (shipped with 7.87.0) and I was certainly in favor of them. I
just think I over time have come to not like them very much anymore.
They also mark a lot of differently deprecated options, so they are used on
options that no longer have functionality as well as options that just are
recommended to not get used. All while our ABI and API promise that we will
not take them away - disambiguous.
I propose we call them not so successful and remove them again:
https://github.com/curl/curl/pull/17141
This is a proposal. I'm eager to learn what you think. Thumbs up or down?
Date: Tue, 22 Apr 2025 23:55:39 +0200 (CEST)
Hello team,
Someone on IRC pointed out that the typecheck-gcc checks don't work anymore. I
could reproduce and I started to fix them. I have a PR pending.
These typechecks warning outputs get pretty damaged by the deprecation
warnings, because they include checks for deprecated options.
This made me realize that I don't think our deprecation warnings do a lot of
good and that they mostly just annoy me when I run into them. We added them in
November 2022 (shipped with 7.87.0) and I was certainly in favor of them. I
just think I over time have come to not like them very much anymore.
They also mark a lot of differently deprecated options, so they are used on
options that no longer have functionality as well as options that just are
recommended to not get used. All while our ABI and API promise that we will
not take them away - disambiguous.
I propose we call them not so successful and remove them again:
https://github.com/curl/curl/pull/17141
This is a proposal. I'm eager to learn what you think. Thumbs up or down?
-- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2025-04-22