[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: automated formatting
From: |
David Kastrup |
Subject: |
Re: automated formatting |
Date: |
Mon, 27 Jan 2020 11:49:00 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Han-Wen Nienhuys <address@hidden> writes:
> I want to propose to move to automated formatting for our C++ code.
>
> I put up a .clang-format code that mostly mimicks our style at
>
> https://codereview.appspot.com/561340043
>
> I have a lot of good experience with automating code formatting.. It
> removes drudgery for code authors, obviates discussions over style in
> code review, and generally elevates the level of discourse in our
> reviews.
>
> What do you all think?
scripts/auxiliar/fixcc.py and astyle 2.04 is what we standardized on.
> The current config modifies about 11k lines, mostly because of
> different line breaks (necessary to keep the 80 column limit.)
Any particular reason to change the automated style to a different one?
Clang is a pretty big dependency for developers.
> If anyone wants to tinker more, see
> https://clang.llvm.org/docs/ClangFormatStyleOptions.html
> for further options.
>
> Obviously, reformatting code makes patches harder to transport, so
> we'd have to do it on all active branches at the same time.
--
David Kastrup
- automated formatting, Han-Wen Nienhuys, 2020/01/27
- Re: automated formatting, Werner LEMBERG, 2020/01/27
- Re: automated formatting,
David Kastrup <=
- Re: automated formatting, David Kastrup, 2020/01/27
- Re: automated formatting, Han-Wen Nienhuys, 2020/01/27
- Re: automated formatting, David Kastrup, 2020/01/27
- Re: automated formatting, David Kastrup, 2020/01/27
- Re: automated formatting, Han-Wen Nienhuys, 2020/01/28
- Re: automated formatting, Carl Sorensen, 2020/01/28
- Re: automated formatting, Dan Eble, 2020/01/28
- Re: automated formatting, David Kastrup, 2020/01/28
- Re: automated formatting, Han-Wen Nienhuys, 2020/01/30