Le 08/09/2017 à 02:24, Martin Thomson a écrit : > On Fri, Sep 8, 2017 at 1:08 AM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote: >> The great majority of code changing is quite expected for any project >> switching to clang-format, since as it turns out automated tools are much >> better at doing this grunt work than humans are. The reason projects choose >> to switch to using clang-format is increasing developer productivity by >> allowing editor/IDE integration for formatting the code as you're editing >> it, ensuring the code formatting remains consistent over time without >> needing to spend invaluable engineering time on it, and being able to stop >> debating whitespace issues and moving on to focus on more productive >> discussions. ;-) > I am 100% behind this idea. NSS is already there and it's so nice. > > One question, because it hurts me every day now, which version of > clang-format will we use? I landed a change to use clang-format 5.0 (we were using a svn version) [1] This can be used with: ./mach clang-format (will run on a diff) ./mach clang-format -p <path> (will run on a path/file)
Some changes landed in 5.0 to manage the Mozilla coding style out of the box (and some options like SplitEmptyFunction only exist in this version). Sylvestre [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1397457 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
