As someone who had to manually ignore uncrustify hooks to get around the
literals issue, I vote +1.
On Fri, Mar 15, 2013 at 1:52 PM, Shazron <shaz...@gmail.com> wrote:
> Might as well take the hit now. no need for code blame - blame usually is
> with the usual suspects (starting with myself of course) ;)
>
>
> On Fri, Mar 15, 2013 at 10:35 AM, Andrew Grieve <agri...@chromium.org
> >wrote:
>
> > Just updated uncrustify from .59 -> .60
> >
> > The good news is it no longer breaks the new Obj-C primitives (@{}, @[]),
> > and it does a better job at ternary ifs.
> >
> > The bad news is that it changes a significant amount of code. Not great
> if
> > we have the code blame changing due to style updates.
> >
> > I think I'd like to try sticking with it and accepting the hit, but
> thought
> > I'd ask what others thinks as well.
> >
>
