Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/1] man/man2/request_key.2: Add missing GNU size forward-declarations
Date: Mon, 14 Sep 2026 15:30:23 +0200	[thread overview]
Message-ID: <aqf1jJ1qxsTdw6kE@devuan> (raw)
In-Reply-To: <20260914122442.GA1591402@pevik>

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

Hi Petr,

> Date: 2026-09-14 14:24:42+0200
> From: Petr Vorel <pvorel@suse.cz>
>
[..]
> Please drop this patch.  I'm sorry, I overlook that although request_key() has
> const char *type like add_key(), unlike it it does not have size.

Thanks!

> Anyway N3207 (spec mentioned in d2c2db883) is something I'll need to get used to :).

There's a more recent paper with a slightly better spec (also compatible
with GCC): N3681.
<https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3681.pdf>

I've improved the GCC documentation, to discourage using several ';',
and added a diagnostic for it, which is in -Wextra:
'-Wmultiple-parameter-fwd-decl-lists'.
See the commit in gcc.git:
33c35b7f4c18 (2025-09-26; "c, objc: Add -Wmultiple-parameter-fwd-decl-lists")

The documentation for the GCC feature is at the bottom of this page:
<https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html>
It's easier to read than the standard specification, IMO.

> 
> Kind regards,
> Petr

Cheers,
Alex

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-09-14 13:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 11:15 [PATCH 1/1] man/man2/request_key.2: Add missing GNU size forward-declarations Petr Vorel
2026-09-14 11:44 ` Alejandro Colomar
2026-09-14 12:24   ` Petr Vorel
2026-09-14 13:30     ` Alejandro Colomar [this message]
2026-09-14 17:19       ` Mark Harris
2026-09-14 18:12         ` Alejandro Colomar
2026-09-14 18:34           ` Martin Uecker
2026-09-14 21:03             ` Alejandro Colomar
2026-09-15  6:08               ` Martin Uecker
2026-09-15  9:02                 ` Alejandro Colomar
2026-09-15  9:45                   ` Martin Uecker
2026-09-15  9:59                     ` Alejandro Colomar
2026-09-15 10:28                       ` Martin Uecker
2026-09-15 10:56                         ` Alejandro Colomar
2026-09-14 18:37         ` status of C forward declarations (was: [PATCH 1/1] man/man2/request_key.2: Add missing GNU size forward-declarations) G. Branden Robinson
2026-09-14 21:06           ` Alejandro Colomar

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=aqf1jJ1qxsTdw6kE@devuan \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=pvorel@suse.cz \
    /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