[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <566E93EB.3000309@users.sourceforge.net>
Date: Mon, 14 Dec 2015 11:03:23 +0100
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: devel@...verdev.osuosl.org,
Andreas Dilger <andreas.dilger@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
kernel-janitors@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Oleg Drokin <oleg.drokin@...el.com>,
Julia Lawall <julia.lawall@...6.fr>,
lustre-devel@...ts.lustre.org
Subject: Re: staging: lustre: Rename a jump label for ptlrpc_req_finished()
calls
>>> Markus, please stop sending these things to rename out labels unless
>>> there is a bug. CodingStyle allows out labels.
>>
>> How does this feedback fit to information like the following?
>>
>> "…
>> Chapter 7: …
>> …
>> Choose label names which say what the goto does or why the goto exists.
>
> A lot of people think "out" says what the goto does and why it exists.
I have got the impression that this short identifier is only partly appropriate.
> I personally don't agree with them
I guess that my opinion goes into a similar direction here.
> but if you look at when I complain about it, it's almost always
> when it causes a bug.
I agree that the combination with bug fixing is more appealing
than an attempt to improve coding style applications.
>> … Avoid using GW-BASIC names …
>
> Those when people just use numbers for their label names instead of
> words like out1, out2, out4, out5. It's a different thing.
The difference is not so clear for me as it appears to you.
How many software developers can still remember habits around
the selection of such identifiers from GW-BASIC times?
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists