Re: coping with different coding styles

On Thu, 1 Dec 2005, Dmitry Beransky wrote:

> 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.

and that was a mistake.

> Unfortunately, and very understandably, this practice wreaks havoc
> when it comes to Subversion's diffs. Is there a good solution to
> this?

define a coding style that everyone must use.

> Maybe a way to normalize the code before it's committed or diff is
> run?

all that's going to accomplish is to allow your programmers to check
in what code that they formatted *one* way, then have to deal with the
reformatted code when they check it back out again. why are you
making life so difficult for yourself?

i mean, the first time a developer checks his code back out again,
he'll have to deal with the new style. why try to avoid this?

rday

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