[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1905131333560.1009@hadrien>
Date: Mon, 13 May 2019 13:36:52 +0200 (CEST)
From: Julia Lawall <julia.lawall@...6.fr>
To: Markus Elfring <Markus.Elfring@....de>
cc: Gilles Muller <Gilles.Muller@...6.fr>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michal Marek <michal.lkml@...kovi.net>,
Nicolas Palix <nicolas.palix@...g.fr>,
Wen Yang <wen.yang99@....com.cn>, cocci@...teme.lip6.fr,
linux-kernel@...r.kernel.org, Yi Wang <wang.yi59@....com.cn>
Subject: Re: [1/5] Coccinelle: put_device: Adjust a message construction
On Mon, 13 May 2019, Markus Elfring wrote:
> >> Thus simplify a message construction in a SmPL rule by concatenating text
> >> with two plus operators less.
> >
> > Is there any way to unindent, so that the string doesn't exceed 80 characters,
> > or at least no so much?
>
> How does your concern fit to the string literal tolerance from
> the Linux coding style?
The point of view of the Linux kernel is that if there is no nicer way to
persent the string, exceeding 80 characters is preferable to breaking the
string. But here, at least if Python was not indentation sensitive, there
are much nicer ways to present the string and not exceed 80 characters.
> > On the other hand, I would have much preferred the original msg = code.
> > I don't understand why it is so offensive.
>
> I suggested again to avoid the use of extra variables in such cases
> (also in the discussed bit of Python source code within a SmPL script).
I realize that you don't like it, although I have no idea why. Does it
make the code slower? Less reliable? Less readable? I doubt any of those
things. I think that staying within 80 characters would be a much greater
benefit that all of these baseless concerns.
julia
>
> Regards,
> Markus
>
Powered by blists - more mailing lists