Thread (22 messages) read the whole thread 22 messages, 8 authors, 2012-05-07

Re: [PATCH] Bluetooth: Fix coding style

From: Arend van Spriel <hidden>
Date: 2012-05-07 10:06:17
Also in: linux-wireless

On 05/07/2012 10:29 AM, Andrei Emeltchenko wrote:
Hi Arend,

On Mon, May 07, 2012 at 10:21:44AM +0200, Arend van Spriel wrote:
quoted
On 05/07/2012 10:14 AM, Andrei Emeltchenko wrote:
quoted
quoted
They don't.  All the examples you'll find are of the form:
quoted
	if (a &&
	    b)

not:

	if (a &&
			b)
Actually it does not look like this, otherwise "b" would be placed in the
same line, don't it?
Let me rephrase Dave's remark so you may understand:

	if (a_has_to_be_long_enough_to_make_you_understand &&
	    you_do_not_care_about_code_readability)

and not:
	if (a_has_to_be_long_enough_to_make_you_understand &&
			you_do_not_care_about_code_readability)
You seems to forgot to reply to the main question about Codying Style.

Best regards 
Andrei Emeltchenko 
True. But you explicitly addressed that one to David. The alignment rule
is indeed not stated in CodingStyle document, but using a seemingly
random amount of tabs is obviously not improving readability. I suppose
the alignment rule with an example could be added to the CodingStyle.

Gr. AvS

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help