[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <06b433109ae9fe821beccb9fd9e3c6a895452a24.camel@perches.com>
Date: Tue, 28 Nov 2023 02:52:00 -0800
From: Joe Perches <joe@...ches.com>
To: Przemek Kitszel <przemyslaw.kitszel@...el.com>,
Andy Whitcroft <apw@...onical.com>,
linux-kernel@...r.kernel.org
Cc: Jacob Keller <jacob.e.keller@...el.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>
Subject: Re: [PATCH] checkpatch: don't complain on _Static_assert and
_Generic use
On Tue, 2023-11-28 at 11:25 +0100, Przemek Kitszel wrote:
> On 11/28/23 01:46, Joe Perches wrote:
> > On Mon, 2023-11-27 at 16:18 +0100, Przemek Kitszel wrote:
> > > Improve CamelCase recognition logic to avoid reporting on _Static_assert()
> > > and _Generic() use.
> > >
> > > Other C keywords, such as _Bool, are intentionally omitted, as those
> > > should be rather avoided in new source code.
> > []
> > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > []
> > > @@ -5839,6 +5839,8 @@ sub process {
> > > #CamelCase
> > > if ($var !~ /^$Constant$/ &&
> > > $var =~ /[A-Z][a-z]|[a-z][A-Z]/ &&
> > > +#Ignore C keywords
> > > + $var !~ /_Static_assert|_Generic/ &&
> >
> > You'll need
> >
> > $var != /^(?:_Static_assert|_Generic)$/ &&
> >
> > to avoid words that contain either
>
> you are correct, thanks
>
> also good to use non-capturing group :), for
Well mostly correct minus the mindless typing of != instead of !~
Powered by blists - more mailing lists