> It doesn't help me all that much to have > familiar formatting and naming in a translation > unit
This is a good skill. But the idea is to help developers that don't have this skill. Philippe On Fri, 22 Jun 2018 19:47:14 +0300 Ville Voutilainen <[email protected]> wrote: > On 22 June 2018 at 19:39, Scott Bloom <[email protected]> wrote: > > I cant even get my developers to agree the emacs takes to many fingers, and > > VI(m) is the only editor they need.... > > > > Let alone, where the brackets and spaces belong.... > > > > Let alone, if statements on the same line as the conditional.... > > > > The problem ive seen, is while you may LOVE the curly brackts on the same > > line, you will never convince me... ?? > > The problem I have with this oft-recurring formatting discussion is > that it's advertised as a big benefit, sometimes > downplaying its cost. It doesn't help me all that much to have > familiar formatting and naming in a translation > unit; that consistency is dwarfed by the effort needed to understand > the logical design of the code to reasonable > modify/refactor/maintain it. > > I think it's reasonable and harmless to clang-format new changes; I > continue to be unconvinced of the cost/benefit ratio > of reformatting all of our existing code. _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
