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: [PATCH] docs: correct symbols-in-versions & doc mismatch for 7.16.4
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Ævar Arnfjörð Bjarmason via curl-library <curl-library_at_cool.haxx.se>
Date: Mon, 02 Aug 2021 11:06:18 +0200
On Fri, Jul 30 2021, Daniel Stenberg wrote:
> On Fri, 30 Jul 2021, Ævar Arnfjörð Bjarmason via curl-library wrote:
>
>> These options introduced in 7.17.0 were documented in 9f44a9552
>> (Renamed several libcurl error codes[...], 2007-08-30) as being
>> introduced in version 7.16.4, but as looking at the 7.16.4 tag and
>> tarball[1] reveals they weren't added until 7.17.0.
>
> This makes me wonder if we're not mostly having a wording issue and
> I'm not sure I agree with your suggested updates.
>
> Let's take the CURLOPT_FTPAPPEND option as an example:
>
>> .SH AVAILABILITY
>> -This option was known as CURLOPT_FTPAPPEND up to 7.16.4
>> +This option was known as CURLOPT_FTPAPPEND up to 7.17.0
>
> The option was called CURLOPT_FTPAPPEND up to *and including* 7.16.4
> from what I can tell.
>
> In 7.17.0, this option had been renamed to CURLOPT_APPEND. I thus
> think the former wording is correct. In 7.16.4 it was
> CURLOPT_FTPAPPEND. Since 7.17.0 we call it CURLOPT_APPEND.
>
> Is this wrong?
No, you're right. I misread that. This proposed patch shouldn't be
included.
For what it's worth this came from skimming a lot of documentation for
symbol names & versions, some of it using "available as of" (or
equivalent) and others "up to" (or equivalent), and my own
misreading/misunderstanding of "up to" meaning "up to and including"
(which seems to be the much less common, but still existent usage).
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-08-02
Date: Mon, 02 Aug 2021 11:06:18 +0200
On Fri, Jul 30 2021, Daniel Stenberg wrote:
> On Fri, 30 Jul 2021, Ævar Arnfjörð Bjarmason via curl-library wrote:
>
>> These options introduced in 7.17.0 were documented in 9f44a9552
>> (Renamed several libcurl error codes[...], 2007-08-30) as being
>> introduced in version 7.16.4, but as looking at the 7.16.4 tag and
>> tarball[1] reveals they weren't added until 7.17.0.
>
> This makes me wonder if we're not mostly having a wording issue and
> I'm not sure I agree with your suggested updates.
>
> Let's take the CURLOPT_FTPAPPEND option as an example:
>
>> .SH AVAILABILITY
>> -This option was known as CURLOPT_FTPAPPEND up to 7.16.4
>> +This option was known as CURLOPT_FTPAPPEND up to 7.17.0
>
> The option was called CURLOPT_FTPAPPEND up to *and including* 7.16.4
> from what I can tell.
>
> In 7.17.0, this option had been renamed to CURLOPT_APPEND. I thus
> think the former wording is correct. In 7.16.4 it was
> CURLOPT_FTPAPPEND. Since 7.17.0 we call it CURLOPT_APPEND.
>
> Is this wrong?
No, you're right. I misread that. This proposed patch shouldn't be
included.
For what it's worth this came from skimming a lot of documentation for
symbol names & versions, some of it using "available as of" (or
equivalent) and others "up to" (or equivalent), and my own
misreading/misunderstanding of "up to" meaning "up to and including"
(which seems to be the much less common, but still existent usage).
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-08-02