Buy commercial curl support from WolfSSL. 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
himself.
Re: What's changing in curl 8
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Stefan Eissing via curl-users <curl-users_at_lists.haxx.se>
Date: Fri, 11 Nov 2022 10:10:01 +0100
> Am 11.11.2022 um 09:52 schrieb Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>:
>
> On Fri, 11 Nov 2022, James Fuller wrote:
>
>> What made curl successful in the past is not necc going to be the same answer in the future ... for example I think considering C99 as the obvious next step (conservative is a good idea) to be somewhat invalid ... if we are to take a great leap I would rather we go straight to C17 which prepares us for changing to C2x. There will be problems, but I am certain they are tractable ... and nothing ventured ...
>
> I'm curious (and ignorant of what these C versions offer): what exactly in those versions do you think would help us?
>
> I personally don't think the C version we use holds us back.
I agree.
Personally, I see many areas where the maintainability of curl (and a lot of the efforts goes into that, afaict) can be improved. And I'd rather spend time on that than solving cross platform C version issues, unless someone can show clear benefits.
There are several proprietary extensions in gcc and clang, namely attribute, that can help catching coding mistakes early. If someone is more expert on that than me, it might be worth looking into how curl can make use of those on targets where they exist, without giving up C89.
Kind Regards,
Stefan
> --
>
> / 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-users
> Etiquette: https://curl.se/mail/etiquette.html
Date: Fri, 11 Nov 2022 10:10:01 +0100
> Am 11.11.2022 um 09:52 schrieb Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>:
>
> On Fri, 11 Nov 2022, James Fuller wrote:
>
>> What made curl successful in the past is not necc going to be the same answer in the future ... for example I think considering C99 as the obvious next step (conservative is a good idea) to be somewhat invalid ... if we are to take a great leap I would rather we go straight to C17 which prepares us for changing to C2x. There will be problems, but I am certain they are tractable ... and nothing ventured ...
>
> I'm curious (and ignorant of what these C versions offer): what exactly in those versions do you think would help us?
>
> I personally don't think the C version we use holds us back.
I agree.
Personally, I see many areas where the maintainability of curl (and a lot of the efforts goes into that, afaict) can be improved. And I'd rather spend time on that than solving cross platform C version issues, unless someone can show clear benefits.
There are several proprietary extensions in gcc and clang, namely attribute, that can help catching coding mistakes early. If someone is more expert on that than me, it might be worth looking into how curl can make use of those on targets where they exist, without giving up C89.
Kind Regards,
Stefan
> --
>
> / 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-users
> Etiquette: https://curl.se/mail/etiquette.html
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2022-11-11