From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>,
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:14:04 +0200 [thread overview]
Message-ID: <551fe7b3-593e-efdf-61e6-199388ab031c@gmail.com> (raw)
In-Reply-To: <5782a3ea-9774-3acb-e365-1e4d03ed3358@gmail.com>
Just forwarding a conversation to the list
On 10/21/21 10:27 AM, Alejandro Colomar (man-pages) wrote:
> Hi Jens,
>
> On 10/21/21 10:17 AM, Alejandro Colomar (man-pages) wrote:
>> Ideally, the standard and the man-pages would have the same
>> prototypes. However, since the standard is not (and cannot be)
>> perfect, when it has some limitations that it cannot overcome which we
>> can, I'll be happy to differ from it. nonnull IMO is very useful in
>> the SYNOPSIS, so I'd like to have it (and I'd also like the standard
>> to have it, but that's likely to take a decade, if it happens at
>> all). Also, the man-pages already use array notation in some specific
>> cases (see pipe(2)), and they are mostly targeted at C programmers, so
>> I think we can safely assume that a C++ reader will know the
>> limitation of its language, and be able to translate C to C++ easily.
>> If any glibc programmer has any concerns regarding that, this is the
>> moment for giving a different opinion :).
>
> I rethinked it a bit after seeing pipe(2) again. I never understood why
> 'static' should be needed at all in an array parameter. The standard
> could have also accepted [26] as requiring at least 26 elements in the
> array, without requiring the use of static. There may be reasons for
> that that I ignore, of course; maybe backwards compatibility.... But
> since the man-pages can present the same information without the static
> keyword, I'll edit my patches to just use [restrict 26], instead of
> [static restrict 26], which is more compact.
>
> BTW, I just noticed that these emails were offlist. If you want to keep
> them offlist, I'l do so, but we typically CC the list to have open
> discussions. If you give me permission, I'll forward these emails to
> the mailing lists.
>
> Cheers,
>
> Alex
>
--
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:14 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 ` [PATCH 1/2] ctime.3: Use VLA notation for [as]ctime_r() buffer Alejandro Colomar (man-pages)
[not found] ` <20c1e58b-ba2b-f9df-ab1f-f80725414cf5@gmail.com>
2021-10-21 9:13 ` Alejandro Colomar (man-pages)
[not found] ` <5782a3ea-9774-3acb-e365-1e4d03ed3358@gmail.com>
2021-10-21 9:14 ` Alejandro Colomar (man-pages) [this message]
[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=551fe7b3-593e-efdf-61e6-199388ab031c@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