|
|
On 9/10/20 10:14 PM Ian MacArthur wrote:
On 10 Sep 2020, at 04:06, markjolesen wrote:
What would be real exiciting is to run it through a source formatter like astyle
OK... um, did note that Albrecht said he’d been running the code through clang-format?
You know that’s a source formatter, like astyle?
Well, yes, I tried it and I prepared a (preliminary) .clang-format file
which I installed in our FLTK root directory.
I'm sure this is not the final setup, there are some points we need to
discuss and there are some cases where we would either re-think the code
formatting (for instance table-like structures of function arguments
etc.) or we'd need to add clang-format directives to disable formatting
in certain places.
Everybody is invited to test: install clang-format if you don't have it,
then run either
$ clang-format `input-file' > `output-file'
or
$ clang-format -i `input-file'
I'm using a graphical diff tool (meld) to compare the result with the
original, YMMV.
I'd appreciate all feedback and suggestions on what of the setup
(.clang-format) to change. TIA.
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/d1581a30-9104-aa26-5b10-76c4ac0f3df8%40online.de.
[ Direct Link to Message ] | |
|
| |