[cvs] bogofilter/src lexer.c,1.54,1.55

[David Relson]

On Mon, 01 Sep 2003 17:56:58 +0200
Matthias Andree <matthias.andree at gmx.de> wrote:

> relson at users.sourceforge.net writes:
> 
> > Update of /cvsroot/bogofilter/bogofilter/src
> > In directory sc8-pr-cvs1:/tmp/cvs-serv32675
> >
> > Modified Files:
> > 	lexer.c 
> > Log Message:
> > Revise indentation.
> 
> Do we want to automate this? We'd have to agree on a common "indent"
> version and could store the corresponding .indent.pro in CVS, and we
> might even use an indent running on SourceForge if they provide for
> this tool - so it's automatic before commit.
> 
> This would eliminate formatting-induced patches.

Auto-indenting of .c and  .h files would be nice.  The following is in
some (many? all?) of our files:

/*
 * The following sets edit modes for GNU EMACS
 * Local Variables:
 * mode:c
 * End:
 */

It seems to work well.  Where we're inconsistent is with compound
statements, e.g.

for (...){
}

or

for (...) {
}

or

for (...)
{
}

For conditionals and loops I like ") {", i.e. paren, space, brace.  For
functions, I like the { at the start of its own line.  I usually format
switches like functions.