[Fwd: Re: Indention - why spaces?]

[Herman Oosthuysen <Herman@WirelessNetworksInc.com>]

Larry McVoy wrote:
> 
> By the way, this sort of thing is a big deal around here, I spend a 
> lot of time getting people to do it all the same way.  It's worth it.
> 

Larry, you can save yourself a lot of trouble, time and money: Create an
indent configuration file and tell your people to use it.  That is
exactly why indent was written many years ago.

Better still, change your commit scripts to automatically run indent
when checking files in.  This works on private projects - it is not
recommended for a public project like GNU/Linux, unless, Linus would
call a halt - indent all files and then carry on, which I'm sure he
won't do, since it is waaaay too much trouble.

With indent, everybody can be happy: You don't like the curly braces
here but rather want them there?  ==> Run indent on your private copy.

BTW, occational windoze users can get the GUIfied 'windent.exe' off my
web site at www.aerospacesoftware.com.  This presents a simple way to
play around with indent; to figure out exactly what schtooopidttt
switches you need to make the code look the way your SQA dork wants...

Also, if you want the whole kernel to be commented and clickable in
html, 'doxygen' does an amazing job with that, even though the kernel
code is not written with doxygen tags.

Since I discovered these two tools, I totally relaxed about code
formatting, since it is simply not an issue anymore.

Cheers,
-- 
Herman