Peter McNab <mcnab_p@melbpc.org.au> writes:
> There has been quite a discussion about adhering to an agreed source
> formatting standard and the hassles that arise from conformance.
> Maybe it's time to adopt a code formatting tool that everyone can use,
> or one that get's used when patches are generated.
> Take the mechanics out of the process so people can concentrate on the
> real work.
Everybody suggests it, no one does it :-).
Seriously: a lot of us have thrown around the idea in a vague sort of
way, but whenever I actually sit down and think of specifics, it gets
hard. Not undoable, just more complex than one might expect. Also,
this hasn't in practice been a big problem (the discussions you've
seen lately have only partly been about the sorts of things that an
automated tool could detect, anyway).
A lot of claims are flying around lately about how picky we are about
formatting. I suggest that before giving the claims too much
credence, people should look over some of our patch- and
commit-reviews themselves and see how much is really about
automatically fixable formatting issues. It's not all that much.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 26 21:07:00 2005