Thanks for putting this together!
It's not obvious to me, though, that it's worth the complexity of
integrating a tool like this into the development workflow; so I'm not
sure I want to accept that patch.
Is the current official code so hard on the eyes? :)
Any other opinions on this question?
On 08/06/2015 03:03 PM, Benjamin Barenblat wrote:
I’ve whipped up a style file for clang-format so we can consistently
format C and JavaScript. I’ve tried to match the existing style as
closely as possible, modulo forcing line wrapping to 80 characters. You
can grab the patch from <http://web.mit.edu/bbaren/c/64148c94.patch>;
its SHA256 sum is
27543c3a30685fd494696d31c5347af8b72c25b89db810371d36bf734f9689f3.
If you’d prefer to replicate my results instead of applying a
172-kilobyte patch, you can just grab the style file out of the diff and
run
find . -name \*.js -or -name \*.c -print0 | xargs -0 clang-format-3.7
-style=file -i
_______________________________________________
Ur mailing list
[email protected]
http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
