[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.22.394.2009291445050.2808@hadrien>
Date: Tue, 29 Sep 2020 14:47:29 +0200 (CEST)
From: Julia Lawall <julia.lawall@...ia.fr>
To: Dan Carpenter <dan.carpenter@...cle.com>
cc: Ard Biesheuvel <ardb@...nel.org>,
Julia Lawall <Julia.Lawall@...ia.fr>,
linux-iio@...r.kernel.org, drbd-dev@...n.linbit.com,
Valdis Klētnieks <valdis.kletnieks@...edu>,
David Lechner <david@...hnology.com>,
Neil Armstrong <narmstrong@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
linux-wireless@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>,
kernel-janitors@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-stm32@...md-mailman.stormreply.com,
linux-block@...r.kernel.org, linux-ide@...r.kernel.org,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
Joe Perches <joe@...ches.com>,
linux-amlogic@...ts.infradead.org,
Thomas Gleixner <tglx@...utronix.de>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
openipmi-developer@...ts.sourceforge.net,
linux-clk@...r.kernel.org,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Jerome Brunet <jbrunet@...libre.com>
Subject: Re: [PATCH 00/18] use semicolons rather than commas to separate
statements
On Tue, 29 Sep 2020, Dan Carpenter wrote:
> On Tue, Sep 29, 2020 at 02:20:00PM +0200, Ard Biesheuvel wrote:
> > On Sun, 27 Sep 2020 at 21:56, Julia Lawall <Julia.Lawall@...ia.fr> wrote:
> > >
> > > These patches replace commas by semicolons.
> >
> >
> > Why?
> >
>
> In the best case, these commas are just uninitentional mess, like typing
> an extra space character or something. I've looked at them before and
> one case I see where they are introduced is when people convert a
> struct initializer to code.
>
> - struct foo {
> - .a = 1,
> - .b = 2,
> ...
> + foo.a = 1,
> + foo.b = 2,
>
> The times where commas are used deliberately to replace curly braces are
> just evil. Either way the code is cleaner with semi-colons.
I also found exaamples like the following to be particularly unforunate:
fprintf(stderr,
"page_nr %lu wrong count %Lu %Lu\n",
page_nr, count,
count_verify[page_nr]), exit(1);
The exit is very hard to see, unless you know to look for it.
julia
Powered by blists - more mailing lists