I only care about reformatting from the perspective of making diffs difficult to read. I'm getting pretty agnostic about it otherwise, as long as the format is neat. I currently prefer braces and same line, and indentation as two spaces, since it makes it much easier for me to cut and paste into presentations ... that's far from an overriding concern.
However, I tend to unconsciously hit the reformat keystroke while I'm thinking, so having a consistent formatting convention will help to reduce unwanted diffs. On Sat, Jul 2, 2011 at 6:01 AM, Massimo Lusetti <[email protected]> wrote: > On Sat, Jul 2, 2011 at 2:04 PM, Bob Harner <[email protected]> wrote: > >> Unless a file is horribly formatted, or else completely new or almost >> completely rewritten, I think reformatting just wastes the time of >> others reading the diffs. All of us are capable of overlooking the >> "wrong" brace style by now. > > It's not just a matter of where are the braces, if it was me it should > be about complete code style(ness) and for about waste of time reading > the diff just read the commit log "style formatting" and you're done. > > Having one only style helps you also discover more bugs which maybe > hidden behind code usage. > > Cheers > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
