Re: coping with different coding styles

Dmitry Beransky <db01@dembel.org> wrote on 02.12.2005 00:15:32:

>
> Commits isn't the only place where different coding style may become a
> problem. A diff between the working base and the working copy can also
get
> screwed up by reformatted code.
>
> I understand that I may need to adopt a coding standard in order to be
> compatible with Subversion. But that was exactly my question: is there
a
> way to make Subversion work the way I want? If the answer is an
absolute
> and definite 'No' then I'll have to change my ways. But then this
smells
> to me as the case of making a developer jump through hoops because tool
> aren't flexible enough instead of having the tools making the
developer's
> life easier (not that Subversion hasn't eased our lives by so much
already
> :-), but we always want more).

If we're talking about modern IDEs, Eclipse has an option to ignore white
spaces during a diff. Maybe your IDE has that option too? Anyway, we also
adopted a uniform coding style, and it wasn't difficult at all. I wonder
if the fact that it was my coding style had anything to do with it? ;-)

Cheers,

---
  Miha Vitorovic
  Inženir v tehničnem področju
  Customer Support Engineer
   NIL Data Communications,  Tivolska cesta 48,  1000 Ljubljana,  Slovenia
   Phone +386 1 4746 500      Fax +386 1 4746 501     http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org