> > In our code base the catch is usually on the next line, we should change > the > eclipse formatter to do that.
:( Also, existing code base does not conform to this standard:) And, although >> I would add bracket forcing for "for" and "if" and others similar >> statements to the current code formatting standard (as a safety measure I >> explained earlier) before reformatting anything, the best example of even >> the current code format would be a formatted code base itself. And yes, a >> check-in hook to be sure it remains so:) >> > > I am actually not to fond of reformatting the entire existing code base, > since > that makes things difficult to diff and changes often don't even improve > the readability. > Notice I didn't propose that. Exactly because I knew the answer in advance :) Aliaksandr
