Names containing a double underscore (__) are reserved to the
C++ implementation, so better just avoid it, even with KATE namespace.
Needs rename of global config include guards to avoid guard name clash.
cullmann |
Kate |
Names containing a double underscore (__) are reserved to the
C++ implementation, so better just avoid it, even with KATE namespace.
Needs rename of global config include guards to avoid guard name clash.
Still builds
Automatic diff as part of commit; lint not applicable. |
Automatic diff as part of commit; unit tests not applicable. |
conjunctive "could" -> not specified in KF policies if possible.
Seems even Qt devs are undecided about it and rejected it again, so myself tend to avoid for now. As much as something like it is desired.
In certain instances #pragma once fails when using MSVC, while traditional #define include guards are fully reliable.
fyi, krazy in strict mode will check for leading and trailing underscores on the include guards.
I don't run krazy in strict mode on the EBN, however.
I could make this a standard check if we want so the EBN would pick it up too.
Thanks!
Qt decided against #pragma once. I wouldn't want to use it in KDE unless it is decided on kde-frameworks-devel.