We tested this with a windows and linux machine using the current master (f94aca1d163721b62e1b05cef36fbe068fea84ed).

This is an example for the resulting activator header:

#ifndef $(activator - file - name) _h
#define $(activator - file - name) _h

#include <ctkPluginActivator.h>

namespace mitk
{
  class $(activator - class - name) : public QObject, public ctkPluginActivator
{

Pushed new branch T22243-PluginGeneratorSymbolicNames.

Pushed new branch T22243-protect-symbolic-names-from-formatting.

We could protect the code from being formatted by surrounding the lines containing the symbolic names with

//clang-format off
Code here...
//clang-format on

However this would result in those comments being transferred to the configured files, where we would not want formatting to be forbidden. Seeing as this should not be much of an issue as this code will be mostly not touched the solution is probably to be careful in future formatting steps.

In T22243#91714, @goch wrote:

We could protect the code from being formatted by surrounding the lines containing the symbolic names with

//clang-format off
Code here...
//clang-format on

However this would result in those comments being transferred to the configured files, where we would not want formatting to be forbidden. Seeing as this should not be much of an issue as this code will be mostly not touched the solution is probably to be careful in future formatting steps.

I think we should do something about it to make sure it doesn't happen again in the future. @goch Just relying on being careful sounds a bit optimistic ;) Just ideas:

• rename all the files from .cpp and .h to .cpp.tmpl -h.tmpl
• provide a target "clang-format" that invokes clang-format correctly on the relevant folders
• write a documentation page on how to use it and how to be careful ;) (if this already exists, I'm sorry, but I couldn't find it ...)

• rename all the files from .cpp and .h to .cpp.tmpl -h.tmpl

@nolden this should be a workable fix for the specific files mentioned in this task.