From: Alejandro Colomar <alx@kernel.org>
To: Martin Uecker <uecker@tugraz.at>,
Christopher Bazley <chris.bazley.wg14@gmail.com>,
Alex Celeste <alexg.nvfp@gmail.com>,
Joseph Myers <josmyers@redhat.com>,
Aaron Ballman <aaron@aaronballman.com>
Cc: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>,
Bruno Haible <bruno@clisp.org>, Paul Eggert <eggert@cs.ucla.edu>,
Florian Weimer <fweimer@redhat.com>,
Jonathan Corbet <corbet@lwn.net>, Kees Cook <kees@kernel.org>,
Eric Biggers <ebiggers@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
Daniel Thompson <danielt@kernel.org>,
Daniel Lundin <daniel.lundin.mail@gmail.com>,
"Valentin V. Bartenev" <vbartenev@gmail.com>,
Andrew Clayton <andrew@digital-domain.net>,
"Brian W. Kernighan" <bwk@cs.princeton.edu>,
"G. Branden Robinson" <branden@debian.org>,
"Basil L. Contovounesios" <basil@contovou.net>,
"Jason A. Donenfeld" <jason@zx2c4.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
onf <onf@disroot.org>, Rich Felker <dalias@libc.org>,
linux-hardening@vger.kernel.org,
Alejandro Colomar <alx@kernel.org>
Subject: [RFC v3 6/6] alx-0080r1 - [static] without array length expression
Date: Mon, 26 Jan 2026 13:49:29 +0100 [thread overview]
Message-ID: <aXdi1kl_wHMFJRFQ@devuan> (raw)
In-Reply-To: <aXdhh1r7ePA5SrIE@devuan>
[-- Attachment #1: Type: text/plain, Size: 2580 bytes --]
Name
alx-0080r1 - [static] without array length expression
Principles
- Keep the language small and simple
Category
Language; array parameters.
Author
Alejandro Colomar <alx@kernel.org>
Cc: Martin Uecker <uecker@tugraz.at>
Acked-by: Doug McIlroy
Acked-by: Andrew Clayton <ac@sigsegv.uk>
History
<https://www.alejandro-colomar.es/src/alx/alx/std/wg14/alx-0080.git/>
r0 (2026-01-25):
- Initial draft.
r1 (2026-01-26):
- Acked-by.
- tfix
Abstract
'static' in [static n] means that the argument shall be
non-null. That is entirely independent of the length of the
array parameter, so it doesn't make sense requiring the length
to be specified. Lift that restriction.
Discussion
While the standard, for a long time, claimed that 'static' in
[static n] was about the length of the array, it is well known
that this is only true in paper. In practice, programmers use
[n] with that meaning.
'static' in [static n] has a different meaning (see also
alx-0079): it says that the argument shall be non-null.
See also
<https://www.alejandro-colomar.es/src/alx/alx/std/wg14/alx-0079.git/>
alx-0079 ("[static n] == non-null [n]")
alx-0079 should be applied before alx-0080. Otherwise, the
semantics would be undefined.
Comments
On 2026-01-25T18:19:02-0500, Douglas McIlroy wrote:
> All six proposals look eminently reasonable. They simplify
> the language and remove surprises. I suspect these proposals
> will invalidate very few existing programs. In any event, the
> required corrections will improve the legibility and
> maintainability of such programs.
>
> Doug McIlroy
---
On 2026-01-26T02:01:16+0000, Alex Celeste wrote:
> Like Martin - these all seem eminently reasonable to me.
Proposed wording
Based on N3685.
6.7.7.1 Declarators :: General
@@ Syntax, p1
+array-qualifier-list:
+ <b>static</b>(opt) type-qualifier-list
+ type-qualifier-list <b>static</b>
+
+array-length-declarator:
+ assignment-expression
+ <b>*</b>
+
array-declarator:
- direct-declarator <b>[</b> type-qualifier-list(opt) assignment-expression(opt) <b>]</b>
- direct-declarator <b>[ static</b> type-qualifier-list(opt) assignment-expression <b>]</b>
- direct-declarator <b>[</b> type-qualifier-list <b>static</b> assignment-expression <b>]</b>
- direct-declarator <b>[</b> type-qualifier-list(opt) <b>* ]</b>
+ direct-declarator <b>[</b> array-qualifier-list(opt) array-length-declarator(opt) <b>]</b>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-01-26 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aXZM5O2mU2e3LJBJ@devuan>
2026-01-26 12:48 ` [RFC v3 0/6] Improve function parameters in ISO C2y Alejandro Colomar
2026-01-26 12:48 ` [RFC v3 1/6] alx-0077r3 - disallow function parameters of function type Alejandro Colomar
2026-01-26 12:48 ` [RFC v3 2/6] alx-0076r3 - incompatible array parameters Alejandro Colomar
2026-01-26 12:48 ` [RFC v3 3/6] alx-0078r2 - [static n] shouldn't access more than n elements Alejandro Colomar
2026-01-28 9:54 ` Daniel Thompson
2026-01-28 15:14 ` Alejandro Colomar
2026-01-26 12:49 ` [RFC v3 4/6] alx-0079r2 - [static n] == non-null [n] Alejandro Colomar
2026-01-26 12:49 ` [RFC v3 5/6] alx-0081r2 - array parameters of 0 elements Alejandro Colomar
2026-01-28 10:14 ` Daniel Thompson
2026-01-28 15:21 ` Alejandro Colomar
2026-01-26 12:49 ` Alejandro Colomar [this message]
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=aXdi1kl_wHMFJRFQ@devuan \
--to=alx@kernel.org \
--cc=aaron@aaronballman.com \
--cc=alexg.nvfp@gmail.com \
--cc=andrew@digital-domain.net \
--cc=ardb@kernel.org \
--cc=basil@contovou.net \
--cc=branden@debian.org \
--cc=bruno@clisp.org \
--cc=bwk@cs.princeton.edu \
--cc=chris.bazley.wg14@gmail.com \
--cc=corbet@lwn.net \
--cc=dalias@libc.org \
--cc=daniel.lundin.mail@gmail.com \
--cc=danielt@kernel.org \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=ebiggers@kernel.org \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=jason@zx2c4.com \
--cc=josmyers@redhat.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=onf@disroot.org \
--cc=torvalds@linux-foundation.org \
--cc=uecker@tugraz.at \
--cc=vbartenev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.