[gmx-developers] Change to clang-format
ericirrgang at gmail.com
Fri Nov 8 08:25:52 CET 2019
Note that many editors already offer clang-format integration that you
might choose to enable. The GROMACS repository now has `.clang-format`
files in place, so no additional configuration should be required to
produce consistently formatted code, no matter how you choose to invoke
Thanks to all who contributed to making this change happen!
On Thu, Nov 7, 2019 at 3:33 PM Paul bauer <paul.bauer.q at gmail.com> wrote:
> Hello developers,
> we are now moving our code formatting style enforcing to use
> clang-format instead of the custom version of uncrustify we have used up
> to now.
> This means that all new code for both master and the release-2020 branch
> that I will create today has to formatted this way.
> We have added a new clang-format.sh script under admin/ to do this, as
> well as updates to admin/reformat_all.sh to change your complete source
> tree to it.
> The information for this can be found here:
> I will remove the information about uncrustify shortly, so that only the
> instructions for clang-format will be there, with a historical note for
> the previous formatting.
> The only things you will need to do is updating the pre-commit hook (if
> you have used this before) to make sure that code is properly formatted
> before uploading.
> Paul Bauer, PhD
> GROMACS Release Manager
> KTH Stockholm, SciLifeLab
> Gromacs Developers mailing list
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> * For (un)subscribe requests visit
> or send a mail to gmx-developers-request at gromacs.org.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gromacs.org_gmx-developers