Rationale: The following code is difficult to read, but allowed by the
current coding style.
if (a == 5) printf(a was 5.\n);
else if (a == 6) printf(a was 6.\n);
else printf(a was something else entirely.\n);
Signed-off-by: Aurelien Jarno aurel...@aurel32.net
---
CODING_STYLE | 10
On Mon, Oct 26, 2009 at 8:26 AM, Aurelien Jarno aurel...@aurel32.net wrote:
Rationale: The following code is difficult to read, but allowed by the
current coding style.
Fully agree.
+Every control flow statement is followed by a new indented and braced
+block; even if the block contains just
On Mon, Oct 26, 2009 at 06:02:52PM +0200, Blue Swirl wrote:
On Mon, Oct 26, 2009 at 8:26 AM, Aurelien Jarno aurel...@aurel32.net wrote:
Rationale: The following code is difficult to read, but allowed by the
current coding style.
Fully agree.
+Every control flow statement is followed by
On Mon, Oct 26, 2009 at 10:03 PM, Aurelien Jarno aurel...@aurel32.net wrote:
On Mon, Oct 26, 2009 at 06:02:52PM +0200, Blue Swirl wrote:
On Mon, Oct 26, 2009 at 8:26 AM, Aurelien Jarno aurel...@aurel32.net wrote:
Rationale: The following code is difficult to read, but allowed by the
current
On Mon, Oct 26, 2009 at 10:20:34PM +0200, Blue Swirl wrote:
On Mon, Oct 26, 2009 at 10:03 PM, Aurelien Jarno aurel...@aurel32.net wrote:
On Mon, Oct 26, 2009 at 06:02:52PM +0200, Blue Swirl wrote:
On Mon, Oct 26, 2009 at 8:26 AM, Aurelien Jarno aurel...@aurel32.net
wrote:
Rationale: The
Aurelien Jarno wrote:
That's the problem. We have seen that people already take advantage of
the ambiguities, as I would have never have imagined someone writing the
code in the rationale of this patch to avoid putting braces.
I appreciate the desire to be precise, but we aren't writing a
