[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: coping with different coding styles

From: Mark Shead <sheadm_at_optimalinternet.com>
Date: 2005-12-01 22:32:45 CET

> With modern IDEs that can change a file's coding style at a press of a
> button, shoehorning a programmer's habits into some arbitrary standard
> made
> no sense to me. So when I set up the development process for our
group, I
> made a decision not to enforce any particular style and let my coders
> choose what works best for them. Unfortunately, and very
understandably,
> this practice wreaks havoc when it comes to Subversion's diffs. Is
there
> a
> good solution to this? Maybe a way to normalize the code before it's
> committed or diff is run? To make things more complicated we access
> Subversion via TortoiseSVN and IntelliJ IDEA.

I would suggest that you create a standard and get everyone to agree to
it. Then implement the standard as setting for the autoformat in your
IDE and as a checkstyle configuration (or some other style tool). That
way your coders have a simple way to format everything correctly and you
can use a pre-commit hook and the checkstyle tool to reject any commits
where they forgot to run the formatter.

--Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 1 22:46:21 2005

This is an archived mail posted to the Subversion Users mailing list.