On Wed, 26 March 2008 12:23:11 +0100, Ingo Molnar wrote:I have an objective reason to prefer one over the other. Your only reason is consistency. If consistency was everything, we might as well let the often-abused 1000 monkeys type up a coding style document and stick to that. But most of our rules exist for reasons beyond mere consistency. Following the rules, on average, makes the code better. In particular the "less" rules (fewer lines, less indentation, etc.) result in more code fitting any arbitrary editor window. Which means more control flow our mind can ponder about without scrolling. Do you have a non-consistency based reason to prefer the longer version? If not, then we should settle on the short version, which does have a minimal advantage. Jörn -- Joern's library part 13: http://www.chip-architect.com/ --
| Brandeburg, Jesse | RE: [regression] e1000e broke e1000 (was: Re: [ANNOUNCE] e1000 toe1000e migration ... |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Valdis.Kletnieks | Re: ndiswrapper and GPL-only symbols redux |
git: | |
| Sander | 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1) |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Paweł Staszewski | rib_trie / Fix inflate_threshold_root. Now=15 size=11 bits |
