uncrustify

[Mark Atwood]

Did Dr Mills have a preferred C style?  If he did, was it not terrible?

What is everyone else's preferred C indent style?

I have my own favorite, but I'm not the one who has to read and rework the
C code.

..m

On Thu, Jan 5, 2017 at 11:18 AM Daniel Poirot <dtpoirot at gmail.com> wrote:

> Before long, everyone will be using a virtual machine with an
> integrated editor and common development system!
>
> ...oh, wait, that's what started all this:
>     https://en.wikipedia.org/wiki/Lisp_machine
>
>
>
> On Thu, Jan 5, 2017 at 12:54 PM, Eric S. Raymond <esr at thyrsus.com> wrote:
> > Hal Murray <hmurray at megapathdsl.net>:
> >>
> >> >> Running  uncrustify against NTPsec is good idea, but it needs to
> >> >> be a flag day, because it will be a huge patch.
> >>
> >> > ...pretty much a 'fork' from which there is no recovery...
> >>
> >> Is that a serious problem?  If so, why?
> >>
> >> It would mean that I couldn't (usefully) diff versions of a file that
> crossed
> >> the flag day, but I don't think I do that very often.  I'm more likely
> to let
> >> git diff version X and X-1 and if we trust uncrustify I won't be doing
> that
> >> for X being the flag day.
> >
> > I concur with Hal's doubt that this is a serious problem.  I don't find
> myself
> > doing diffs with very old versions often.  If I did, diff -b (ignoring
> > whitespace) would probably mitigate a lot of them.
> >
> > I've installed uncrustify.  I'll do some experoments.
> > --
> >                 <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
> _______________________________________________
> devel mailing list
> devel at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20170105/0b29d728/attachment.html>