From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH 1/2] ctime.3: Use VLA notation for [as]ctime_r() buffer
Date: Thu, 21 Oct 2021 11:12:54 +0200 [thread overview]
Message-ID: <4ea614e0-02d7-ec82-5fc7-307403d8dccc@gmail.com> (raw)
In-Reply-To: <20211021092746.78bc82f8@inria.fr>
Just forwarding a conversation to the list
On 10/21/21 9:27 AM, Jₑₙₛ Gustedt wrote:
> Hello Alejandro,
>
> On Wed, 20 Oct 2021 22:22:40 +0200, Alejandro Colomar wrote:
>
>> As N2417 (part of C2x) suggests. This syntax is very informative,
>> and also, if used by library implementers, can improve static
>> analysis.
>>
>> Since it is backwards compatible with pointer syntax, we can do this.
>
> I understand the intent, but these `_r` interfaces finally went into
> the standard without array notation. AFAIR one of the arguments was
> that the headers should be usable from C++.
>
> So I am not sure if it is consensus to have the documentation have a
> different form of the interfaces than the standard(s). I don't know if
> you'd also add the attributes that glibc uses to the `printf`
> interfaces, for example.
>
> I am not saying that you shouldn't, in the contrary it is probably a
> good idea to list all those semantic restrictions in the documented
> interface for which me have syntax. I just want to make sure that
> adding such semantic hints to the documentation is consensus and
> sufficiently well discussed.
>
> Thanks
> Jₑₙₛ
>
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-10-21 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 20:22 [PATCH 1/2] ctime.3: Use VLA notation for [as]ctime_r() buffer Alejandro Colomar
2021-10-20 20:22 ` [PATCH 2/2] ctime.3, strftime.3, strptime.3, timegm.3: Add [[gnu::nonnull]] to <time.h> prototypes Alejandro Colomar
2021-10-21 8:13 ` AW: " Walter Harms
2021-10-21 9:01 ` Alejandro Colomar (man-pages)
2021-10-21 17:40 ` Paul Eggert
2021-10-21 20:54 ` Alejandro Colomar (man-pages)
[not found] ` <20211021092746.78bc82f8@inria.fr>
2021-10-21 9:12 ` Alejandro Colomar (man-pages) [this message]
[not found] ` <20c1e58b-ba2b-f9df-ab1f-f80725414cf5@gmail.com>
2021-10-21 9:13 ` [PATCH 1/2] ctime.3: Use VLA notation for [as]ctime_r() buffer Alejandro Colomar (man-pages)
[not found] ` <5782a3ea-9774-3acb-e365-1e4d03ed3358@gmail.com>
2021-10-21 9:14 ` Alejandro Colomar (man-pages)
[not found] ` <20211021110311.52541d69@inria.fr>
[not found] ` <ec620c5e-0952-fe16-353c-0210d3bea6e8@gmail.com>
2021-10-21 9:27 ` Alejandro Colomar (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ea614e0-02d7-ec82-5fc7-307403d8dccc@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jens.gustedt@inria.fr \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).