David Brownell wrote:
Or in other words:
- When a new scope is opened, increase indentations by 8 characters.
Use a tab for that.
- When wrapping within an expression, start the new line at the same
column at which the (sub-)expression started.
- Deviations from the latter rule allowed if it increases readability.
> Please change your coding style to conform to Documentation/CodingStyle.
I won't change this anymore in any legacy code I write patches for. But
I also won't stand in the way of anybody who happens to submit patches
which strictly only...
> *** Only indent with tabs!! ***
...indent with tabs and change legacy code whose maintainer I am.
> Every one of those examples violates that simple rule.
/Does/ anybody have difficulties?
...
What I said at the top of this posting has not been newly grown recently
but has been common practice for many years. It's not my personal style.
(Note, I'm not saying one style is better than the other, nor am I
saying that only one style can be allowed, nor am I saying that it's
fine to have several different styles.)
--
Stefan Richter
-=====-=-=== -=-- --==-
http://arcgraph.de/sr/
-
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Linus Torvalds | Linux 2.6.27-rc5 |
| Jared Hulbert | [PATCH 00/10] AXFS: Advanced XIP filesystem |
| Linus Torvalds | Linux 2.6.27-rc8 |
git: | |
| David Miller | [GIT]: Networking |
| Antonio Almeida | HTB accuracy for high speed |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
