Re: [pilot-db-list] CVS indentation strategy

[Mariusz S. <MSt...@zn...>]

	As a new (and very impressed) user of Pilot-DB, I have just subscribed
to this list, so hello all.
	The subject of coding style, as much as a choice of an programmer's
editor has been a flash point for many a flame war, yet the idea of coding
standardization is a compelling one, but a choice (any choice!) of even
among the four major (not counting variants) coding styles will leave the
proponents of the other three less happy.
	There is a solution, though, that bypasses the whole issue; namely,
source code reformatters.  One particular implementation of this idea has
served me well over the years in the Windows environment (*nix has a
similar one (part of GNU utilities) which name escapes me now).  Christophe
Beaudet' s GC (for Great Code) can be found at
http://perso.club-internet.fr/cbeaudet is NOT an open source utility, but
is free to use.  It is a very versatile command line utility that does a
near perfect (you know, like that 99% accuracy OCR) job.  No, really; It
has very few quirks, and it excels at straight C code... good enough to do
a wholesale batch convert between styles.

/Mariusz

P.S. Is there a way to get past posting to this list... Mailman comes up
short on this.

On Sat, 21 Feb 2004 20:33:11 -0800, Tony McNamara wrote:

>We'd never get a standardized indentation style working.  I personally 
>have used four spaces (no tabs) for decades, along with the old 
>structured-C style braces (braces on their own lines), and find the BSD 
>style function header line of type\nname(args){\n utterly 
>incomprehensible even though I do a lot of commercial work on BSD. 
>
>The open-source world is full of opinions, but there's no way to enforce 
>a standard when all the work is charity.  So I would say do whatever you 
>feel necessary for legibility and always use the -w parameter with cvs 
>diff.  (That ignores all whitespace differences.)