From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org
Cc: Jacob Keller <jacob.e.keller@intel.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] checkpatch: don't complain on _Static_assert and _Generic use
Date: Wed, 29 Nov 2023 09:58:23 +0100 [thread overview]
Message-ID: <713eb42d-114b-4738-92ab-242d73fe71ce@prevas.dk> (raw)
In-Reply-To: <20231127151847.52945-1-przemyslaw.kitszel@intel.com>
On 27/11/2023 16.18, Przemek Kitszel wrote:
> Improve CamelCase recognition logic to avoid reporting on _Static_assert()
> and _Generic() use.
>
_Generic I understand, because that can reasonably be used in new macros.
But is there ever any reason for introducing new uses of _Static_assert
when we already have the static_assert() wrapper? Shouldn't people use
that instead of the raw keyword?
> Other C keywords, such as _Bool, are intentionally omitted, as those
> should be rather avoided in new source code.
... in exactly the same way that we have 'typedef _Bool bool;' and then
prefer people to spell it 'bool'.
Rasmus
prev parent reply other threads:[~2023-11-29 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:18 Przemek Kitszel
2023-11-28 0:46 ` Joe Perches
2023-11-28 10:25 ` Przemek Kitszel
2023-11-28 10:52 ` Joe Perches
2023-11-29 0:48 ` Joe Perches
2023-11-29 8:58 ` Rasmus Villemoes [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=713eb42d-114b-4738-92ab-242d73fe71ce@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=przemyslaw.kitszel@intel.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
all inboxes | Powered by JetHome®