Re: [PATCH/v2] CodingStyle updates

Scott Preece wrote:
> I think the mistake illuminates why parentheses should be the rule. If
> you're thinking about using spacing to convey grouping, use
> parentheses instead...

But then, we do reflect operator precedence by omitting whitespace
around . and ->, before [], or after unary & and *.
-- 
Stefan Richter
-=====-=-==- ==-- -====
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH/v2] CodingStyle updates
    • From: Randy Dunlap <[email protected]>
  • Re: [PATCH/v2] CodingStyle updates
    • From: Pavel Machek <[email protected]>
  • Re: [PATCH/v2] CodingStyle updates
    • From: Stefan Richter <[email protected]>
  • Re: [PATCH/v2] CodingStyle updates
    • From: Pavel Machek <[email protected]>
  • Re: [PATCH/v2] CodingStyle updates
    • From: "Scott Preece" <[email protected]>

• Prev by Date: Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)
• Next by Date: Re: [PATCH/v2] CodingStyle updates
• Previous by thread: Re: [PATCH/v2] CodingStyle updates
• Next by thread: Re: [PATCH/v2] CodingStyle updates
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]