woods@most.weird.com (Greg A. Woods) writes:
> In this particular case I've never ever been shown any rational for
> using a tab.  The only one I've ever been able to imagine is that if you
> have a collection of #define and #undef lines interleaved together then
> it might be nice to have the second token alligned and thus a tab before
> every token would be the most consistent form.  However I never mix a
> group of #define and #undef lines.

Another that's nice is that they do the right thing re: alignment, for
diffs.

e.g.
#define<tab>name<tab[s]>value

for instance:

#define<tab>foo<tab>baz     
#define<tab>barfoo<tab>baz

becomes:

  #define       foo     baz
  #define       barfoo  baz

but if you use spaces instead of the tabs after the #defines you get:

  #define foo   baz     
  #define barfoo        baz

(of course, you could use spaces after the names being defined, but
I'm really not keen on that...  having to realign using spaces is
... annoying, to say the least.)

-- 
Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html
Disclaimer: Not speaking for NetBSD, just expressing my own opinion.