Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • 3
    Yes. No. Both answers are equally valid. Just pick something and stick to it. Commented Apr 22, 2015 at 12:50
  • Write a script that does it for you, eg corrects tabs and spaces, line endings, etc, to your set standard... then as already mentioned be consistent from now on. I recommend you don't ignore changes to whitespaces with git... every little helps when debugging :) Commented Apr 22, 2015 at 13:04
  • @G.Rassovsky I'd tend to suggest doing it in the IDE that is being used along with the use of checkstyle to enforce it. A script to do it is fun, but its a solved problem as part of the IDE formatting. As long as everyone is using the same formatter settings in the IDE (and verifying it with tools designed to do so), it shouldn't be an on-going problem after the Great Reformation Commit. Commented Apr 22, 2015 at 13:12
  • oh yeah, that's correct, what i meant is don't do it manually :)... if any IDE/tool is already capable of providing results they are happy with then, by all means use it. No point in rediscovering America Commented Apr 22, 2015 at 13:16
  • 1
    First question which comes into my mind is - why does "your editor" now has problems? 1m+ SLOC were not in written in one day - why was your team not interested in fixing this problem earlier? Do you use a different editor than the rest of your team? So when your team has consensus about this, then is answer is yes, and when they don't have consensus, then the answer is "no" or at least "not now". Commented Apr 22, 2015 at 13:30