From: Alejandro Colomar <alx@kernel.org>
To: Martin Uecker <uecker@tugraz.at>
Cc: Mark Harris <mark.hsj@gmail.com>, Petr Vorel <pvorel@suse.cz>,
linux-man@vger.kernel.org, Yeoul Na <yeoul_na@apple.com>,
John McCall <rjmccall@apple.com>
Subject: Re: [PATCH 1/1] man/man2/request_key.2: Add missing GNU size forward-declarations
Date: Tue, 15 Sep 2026 12:56:57 +0200 [thread overview]
Message-ID: <aqkjVw72crIamoKm@devuan> (raw)
In-Reply-To: <1bb001e8c067ac5f91ff7765979289f1bb8f8628.camel@tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
Hi Martin,
> Date: 2026-09-15 12:28:31+0200
> From: Martin Uecker <uecker@tugraz.at>
>
[...]
> > > But then again, it seems very unlikely that writes
> > >
> > > enum { MAX_DIMS = 100 };
> > >
> > > void i(int a[MAX_DIMS], int MAX_DIMS);
> > >
> > > with the intention that the first MAX_DIMS actually
> > > refers to the global variable and not to the parameter.
> > > If such code exits, it is almost certainly already an
> > > unintentional error.
> >
> > And you would not diagnose such an unintentional error?
>
> This would not be a new error, but an old one.
> Nobody felt the need to diagnose this in the last four decades.
> And after the change, it would not be an error, so there seems
> even less reason to diagnose it.
If retroactive scoping is added but optional (to allow small compilers
to live without it), then it might become a problem. Porting code using
it to compilers not supporting it might successfully compile, but have
different semantics.
[...]
>
> QoI might result in diagnostic if it turns out to be a problem.
But I would be okay, since indeed QoI would come to save us.
> But if it were a real issue, we would have the diagnostic already.
Cheers,
Alex
>
> Martin
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-15 10:57 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
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 [this message]
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=aqkjVw72crIamoKm@devuan \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mark.hsj@gmail.com \
--cc=pvorel@suse.cz \
--cc=rjmccall@apple.com \
--cc=uecker@tugraz.at \
--cc=yeoul_na@apple.com \
/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